Loading the registry…
Regenerate and verify attacksurface.md — the estate-wide map of everything deployed across Fredis, saulera, VTV, merkle-email-hub and mission-control (hosts, vendors, sites, CI, cron/agent jobs; each entry carries auth, creds location, reachability, blast radius, re-test cadence). Run QUARTERLY, and on any trigger: a new systemd/launchd unit or listening port appears; a credential-file's perms drift off 600; a new inbound endpoint, webhook, Pages Function, vendor or third-party account is added; a deploy path changes (Actions dies or recovers, a deploy key rotates); a secret is added to .env or rotated; a repo flips public/private or loses branch protection; or before promoting any agent-autonomy rung. Produces a diff against the previous attacksurface.md plus a hand-off command block for the VPS and account checks the agent is hook-walled from. Use when the user says "attack surface", "security audit", "re-audit the estate", "what is deployed", or "refresh attacksurface.md".
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.
337 critical findings reported by cisco-skill-scanner, agent-audit-kit, 41 of them in the installed artifact. 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 -- attack-surface-audit
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- attack-surface-audit ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
5 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.
v1.4.0
Incomplete run
0 findings · 1.4s
v2.0.11
629 findings · 93.0s
v0.3.26
391 findings · 36.8s
v0.1.0
0 findings · 18.2s
v0.1.0
33 findings · 18.2s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.2s
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 14, 2026 | Scan Halted | — | agentshield ·!: incompletecisco-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 1,053 findings above stand exactly as their scanners reported them, at full severity.