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.
npx agentmods add skills/random6913/claude-code-superkit/audit-backendnpx skills add RaNDoM6913/claude-code-superkit --skill audit-backendgit clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkitWhat 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 | $0.00026 | $0.00903 |
| Opus 5 | $0.00013 | $0.00451 |
| Sonnet 5 | $0.00005 | $0.00181 |
| Haiku 4.5 | $0.00003 | $0.00090 |
Grade B, and why
audit-backend scanned grade B with 1 finding 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 yesterday.
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.
Harvests environment variablesmediumData exfiltration
Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.
Extract all environment variable references from source code. Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Audit
Audit backend source code for SQL safety, error handling, API contract integrity, and convention violations.
Detection Strategy
Auto-detect the backend stack by scanning for:
go.mod— Go projectpackage.jsonwith Express/Fastify/NestJS — Node.js projectrequirements.txt/pyproject.tomlwith Flask/FastAPI/Django — Python projectCargo.toml— Rust projectpom.xml/build.gradle— Java project
Identify source directories, handler/controller locations, service layers, and data-access layers.
Checks
1. SQL Injection Risk
Grep for SQL built with string interpolation:
- Go:
fmt\.Sprintf.*(?:SELECT|INSERT|UPDATE|DELETE) - JS/TS:
`SELECT.*\$\{|`INSERT.*\$\{|`UPDATE.*\$\{|`DELETE.*\$\{ - Python:
f"SELECT|f"INSERT|"SELECT.*".format|%s.*SELECT(outside ORM) FAIL for any SQL built with user input via string interpolation.
2. DELETE without WHERE
Grep DELETE FROM in data-access/repository files and verify each has a WHERE clause.
FAIL for any unguarded DELETE statement.
3. Unbounded SELECT on Large Tables
Grep SELECT.*FROM without LIMIT in repository/data-access files.
WARN for queries on potentially large tables without pagination or limits.
4. Swallowed Errors
- Go: grep
_ = err(excluding test files) - JS/TS: grep
catch\s*\(with empty or log-only bodies - Python: grep
except.*:.*pass$|except.*:.*continue$WARN for each occurrence — errors should be wrapped or handled.
5. Debug Print Statements
- Go: grep
fmt\.Print|log\.Print(should use structured logger like zap/zerolog) - JS/TS: grep
console\.login server-side code - Python: grep
print(in non-CLI code (should use logging module) WARN with count — should use structured logging.
6. Missing Error Wrapping
Grep for bare error returns without context wrapping:
- Go:
return.*err$withoutfmt.Errorforerrors.Wrap - JS/TS:
throw errwithout additional context Sample 5 files. WARN for pattern violations.
7. Stub/NotImplemented Endpoints
Grep NotImplemented|TODO.*endpoint|stub|placeholder in handler/controller files.
WARN for each stub that is routable (reachable by clients).
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.
- yesterday First seen · 94 lines · 26 tokens per session scan B 130e2c588bf5
audit-backend is a skill published in the GitHub repository RaNDoM6913/claude-code-superkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 903 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (harvests environment variables). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
apm-review-panel
Use this skill to run a multi-persona expert advisory review on a labelled pull request in microsoft/apm. The panel fans out to five mandatory specialists plus a test-coverage specialist (active on every PR that touches src/) plus three conditional specialists (auth, doc-writer, performance-expert), all running in…
apm-issue-autopilot
Use this skill to drive any open microsoft/apm issue (bug, feature, docs, refactor, perf) from raw intake to a mergeable PR with triage as the central, paramount gate. Run the apm-triage-panel rubric per issue first, then present ONE consolidated triage review for the whole batch and escalate to the maintainer BY…
apm-spec-guardian
Use this skill to run a four-panel adversarial advisory review on any pull request that touches the OpenAPM specification artifact (docs/src/content/docs/specs/openapm-.md), its inline / sidecar JSON Schemas (docs/src/content/docs/specs/schemas/.schema.json), or the conformance fixture seed…
apm-triage-panel
Use this skill to triage one microsoft/apm issue selected by the daily sweep, the status/needs-triage fast path, or manual dispatch. Emit one synthesized comment with a decision, label set, exact milestone, and suggested next action.
batch-bug-shepherd
Use this skill to drive a batch of suspected bugs in microsoft/apm from raw issue list to mergeable PR queue. Fan out one triage subagent per issue (LEGIT / UNCLEAR / FIXED-AT-HEAD), gate every legit bug against PRINCIPLES.md via an apm-ceo strategic-alignment pass, cross-reference legit issues against open PRs, then…
cli-logging-ux
Use this skill when editing or creating CLI output, logging, warnings, error messages, progress indicators, or diagnostic summaries in the APM codebase. Activate whenever code touches console helpers (richsuccess, richwarning, richerror, richinfo, richecho), DiagnosticCollector, STATUSSYMBOLS, CommandLogger, or any…