audit-dependencies
Skill6 starsChanged 2 days agoMITView on GitHub
Use when the user requests a Version Sentinel dependency audit or sees "Version Sentinel startup audit failed", missing or expired audit evidence, or dependency work blocked by the startup audit.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- danygiguere/audit-skillstheir own version, first seen Nov 16, 2026
- krzysztofsurdy/code-virtuosotheir own version, first seen Nov 1, 2026
- mia-cx/skillstheir own version, first seen Oct 16, 2026
- tejastn10/workbenchtheir own version, first seen Oct 13, 2026
- Peter537/peter537-agent-plugintheir own version, first seen Oct 11, 2026
- payloadcms/payloadtheir own version, first seen Oct 8, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- payloadcms/payload★ 46ksame name
- krzysztofsurdy/code-virtuoso★ 36same name
- BerryKuipers/claude-code-toolkit★ 7same name
- danygiguere/audit-skills★ 7same name
- mia-cx/skills★ 4same name
- tejastn10/workbench★ 1same name
- Peter537/peter537-agent-plugin★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- audit-dependenciesSkill
- version-sentinelSkill
- version-sentinelSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Run the online audit for the user's current project and report the result.
- Distinctive: line 12
Use the project directory named in the startup warning or the user's request.
- Distinctive: line 14
Run through Bash, quoting both paths:
- Distinctive: line 28
Do not disable hooks, bypass verification, edit evidence by hand, or change dependencies to make the audit pass.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Audit dependencies
Run the online audit for the user's current project and report the result. The audit records evidence in .version-sentinel/audit.json; it does not install packages or change dependency versions.
Run the audit
- Use the project directory named in the startup warning or the user's request. Keep that directory as the command's working directory; do not audit the plugin installation.
- Locate the script bundled with this skill. In a plugin install it is
../../scripts/check-versions.shrelative to this skill's directory. In the repository's.agents/skills/copy it is../../../scripts/check-versions.sh. Resolve the script to an absolute path. Do not select an older./scripts/check-versions.shjust because it exists in the user's project, or assume plugin environment variables are set in the terminal. Run through Bash, quoting both paths:
cd "<project-directory>" && bash "<absolute-plugin-root>/scripts/check-versions.sh"Inside Codex, the script reads
CODEX_THREAD_IDautomatically. Keep the current session identity; do not invent one or copy audit evidence from another project.
Report the result
- Report the exit status and the specific diagnostic.
DRIFT,UNPINNED, andintentional-pinrows alone do not fail the audit or authorize upgrades. - Report completion only when the command exits 0 and prints
mandatory online dependency audit completed. A silent exit 0 can mean the plugin is disabled; report that the audit was skipped, without changing the disable setting or claiming current evidence. Separate package-version recording is still required before dependency changes. - On failure, keep dependency work blocked. Report registry or prerequisite failures with the retry command. For parser limitations, preserve manifests and npm overrides and report the tool limitation. Missing or invalid manifests need the user's approval before repair or recreation.
Do not disable hooks, bypass verification, edit evidence by hand, or change dependencies to make the audit pass. After the reported cause is resolved, rerun this same command.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

