flox agent audit runs NVIDIA SkillSpector over each skill and the rest of what the plugin carries, and scores it from 0 to 100, where higher is better.
Install the scanner
The audit needs theskillspector program and network access to api.osv.dev, which it uses for live vulnerability data.
Install SkillSpector into your environment:
Audit a package before installing it
Name the catalog package. Flox fetches it into a temporary environment, audits it, and deletes the temporary environment afterwards:@<version> to audit a specific version, for example agent-stacks/agent-plugin-caveman@4.0.1.
Audit what is already installed
Pass a file path instead of a package name. To audit one installed plugin:flox agent audit frontend-design looks in the catalog, not in your environment.
Read the result
Each skill and component gets its own score, and the plugin scores its worst. The bands are SkillSpector’s:
Findings are listed with their severity, rule, and the file and line that matched.
HIGH and CRITICAL findings move the score most.
For a
caution score, read each finding and decide whether the skill’s text justifies it.
The audit also says what it did not check.
It scans the plugin’s skills, its hooks, agents and commands, a bin/ with programs of its own, and other folders such as scripts/ and src/.
MCP server configuration and files outside the plugin layout, such as README.md, are listed under “Not checked”, and the score says nothing about them.
Nothing is executed, and no language model reads the plugin.
Gate on a score in CI
--threshold makes the audit exit with status 1 when the score is below the number you give:
safe.
On a slow runner, give each scan more time with --scan-timeout, for example --scan-timeout 15m.
Related
flox agent auditreference, including the JSON output and exit codesflox agent check-plugin, which checks that a plugin follows the specification rather than whether it is safe