Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkitWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/random6913/claude-code-superkit/security-scan)<a href="https://agentmods.dev/commands/random6913/claude-code-superkit/security-scan"><img src="https://agentmods.dev/badge/commands/random6913/claude-code-superkit/security-scan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/random6913/claude-code-superkit/security-scan"><img src="https://agentmods.dev/badge/commands/random6913/claude-code-superkit/security-scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00023 | $0.01336 |
| Opus 5.5 | $0.00009 | $0.00534 |
| Sonnet 5.5 | $0.00005 | $0.00267 |
| Haiku 4.5 | $0.00002 | $0.00134 |
Grade A, and why
security-scan scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Scan
Run AgentShield to audit .claude/ configurations for vulnerabilities (102 rules, 5 categories), then report the score and findings.
Target
$ARGUMENTS
Hard Rules
- Report ONLY what the scanner actually output — never invent a score, grade, or finding. If the scan cannot run or exits with an error, report that error and stop.
- AgentShield grades on its own scale
critical / high / medium / low. Relay it verbatim; do NOT remap it to the kit's CRITICAL / WARNING / SUGGESTION. - Run the scan at most once, using the single Step 2 command that matches the flags in Target.
--opusneedsANTHROPIC_API_KEYset in the environment; if it is unset, run without--opusand say so.- Emit the report only after the scan command has actually returned.
Step 1 — Check AgentShield availability
npx ecc-agentshield --version
Branch on the result:
- Prints a version → installed; go to Step 2.
- Errors because the package is not cached yet →
npxwill downloadecc-agentshieldon first run in Step 2; go to Step 2. npxunavailable, no network, or download fails → reportAgentShield unavailable: <error>and stop. Do not fabricate results.
Done when: you know whether the scan can run.
Step 2 — Run the scan
Select ONE command by the flags in Target (flags are independent; if Target names more than one, append each form to the single scan command):
| Flag in Target | Command |
|---|---|
| (none) | npx ecc-agentshield scan |
--fix |
npx ecc-agentshield scan --fix — auto-remediate safe issues |
--opus |
npx ecc-agentshield scan --opus --stream — AI deep analysis (needs ANTHROPIC_API_KEY) |
--format json |
npx ecc-agentshield scan --format json — for CI integration |
--format markdown |
npx ecc-agentshield scan --format markdown — for reports |
If the command exits non-zero for a reason other than findings-present (e.g. a crash), report the exit code and stderr; do not invent a score.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 143 lines · 23 tokens per session scan A 51d680b0d6ea
security-scan is a command published in the GitHub repository RaNDoM6913/claude-code-superkit (3 stars, last pushed 3d ago), licensed MIT. It adds 23 tokens to every session and 1,336 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
handoff
Hand off a task to another workspace with an LLM-written summary.
vault
Build/refresh a unified Obsidian vault (knowledge + all repo wikis).
send
Send a message to another Conductor workspace.
capture
Model-driven lesson capture — read recent work in a role, distill genuine insights, append tagged bullets to pending.md. The real capture path; complements the Stop-hook's cheap regex fast-lane.
org-map
Render a shareable org-map SVG (ORGMAP.svg) of this repo's org — roles, projects, captured lessons, token savings. Built to screenshot and post.
turing-save
Manually preserve session state and create ADRs for architecturally significant decisions using the TURING protocol.