Loading the registry…
Audit an existing repo's agent infrastructure — CLAUDE.md, hooks, settings.json, memory files, project-local skills — against instruction-budget and enforcement doctrine. Run periodically, and after any change to CLAUDE.md, settings.json, a hook, or a memory file. Triggers: "audit this repo's setup," "is our CLAUDE.md too long," "check our hooks actually fire," "why does the agent ignore our rules." Twelve checks: instruction budget, duplication against the global CLAUDE.md, prose rules that should be hooks, hook validity and fire tests, false enforcement claims, memory shape and staleness, precedence coherence, project skill economics, stale pointers, growth discipline, verification placement, and evidence reach (rules that never travel to the subagents they bind, merge gates resting on memory not a fresh marker, claims from a surface that cannot produce them validly). Reports PASS or BLOCK with severity-ranked findings, the exact fix per finding, and what already passes. Read-only: diagnoses, does not edit.
Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
3 critical findings reported by cisco-skill-scanner, agent-audit-kit. The composite score alone does not reflect this — read the per-scanner reports below.
Claude Skills install to a single target, no runtime picker.
nerlo install -- 'y-b-1/charge (agent-config-audit)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'y-b-1/charge (agent-config-audit)' ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
4 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v2.0.11
66 findings · 11.0s
v0.3.74
5 findings · 2.6s
v0.1.0
0 findings · 4.2s
v0.1.0
8 findings · 4.2s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image, nerlo-multi-source.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 16, 2026 | Scan Halted | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicable | rejected |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
This review has not run for this scan yet. It runs once per scan, in the background, and is kept; it appears here when it has. Until then all 79 findings above stand exactly as their scanners reported them, at full severity.