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 skills add GoldenWing-360/claude-security-skills --skill codebase-auditgit clone --depth 1 https://github.com/GoldenWing-360/claude-security-skillsWrote 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/skills/goldenwing-360/claude-security-skills/codebase-audit)<a href="https://agentmods.dev/skills/goldenwing-360/claude-security-skills/codebase-audit"><img src="https://agentmods.dev/badge/skills/goldenwing-360/claude-security-skills/codebase-audit/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/skills/goldenwing-360/claude-security-skills/codebase-audit"><img src="https://agentmods.dev/badge/skills/goldenwing-360/claude-security-skills/codebase-audit.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.00093 | $0.04759 |
| Opus 5 | $0.00046 | $0.02380 |
| Sonnet 5 | $0.00019 | $0.00952 |
| Haiku 4.5 | $0.00009 | $0.00476 |
Grade A, and why
codebase-audit scanned grade A with 2 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
$ curl -H "Cookie: $A_SESSION" https://app.example.com/api/invoices/$B_INVOICE_ID Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
grep -rEn 'child_process|execSync|spawn|popen|os\\.system|subprocess\\.(run|call|Popen)' --include='*.{js,ts,py}' . | head How it starts
The opening of the file, as written. The whole thing — 419 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Audit — the Inherited-Code Playbook
This is the skill that binds the others together. Most engagement value from a security review comes from the auditor's process, not from any single check. A junior auditor with a great tool produces a noisy report; a senior auditor with grep and a methodology finds the things that matter.
This skill is the methodology. It walks the audit from "I just got SSH access / a repo URL" through to "here's the prioritized report with owners and deadlines." It cross-links into every hardening skill in this repo as the deep-dive material per finding class.
When to invoke
- Inheriting a codebase — new job, new client, open-source fork, acquisition target
- "Audit my app" engagement — freelancer / consultancy work
- Onboarding to a project — you'll touch the code soon and need to know what's safe to assume
- AI-generated codebase review — before shipping a Claude/Copilot/Cursor-written app
- Periodic re-audit — annual review of a system you already know
Step 0 — Scope before substance
The most common reason audits fail is the auditor trying to look at everything. Scope discipline is the difference between a useful report and a 300-page document nobody reads.
Before starting, write down:
- Why this audit exists — diligence? incident? compliance? onboarding?
- Who reads the report — engineers? CTO? legal? buyer?
- Time budget — 4 hours? 4 days? 4 weeks? This determines depth.
- What's in scope — which repos / services / domains / accounts. Get it confirmed in writing.
- What's explicitly out of scope — third-party SaaS, customer data, anything the client did not authorize. Get this confirmed too.
- Deliverable shape — report? findings spreadsheet? remediation PRs? presentation?
Without these five answers, do not start. Time spent here saves three times that later.
Step 1 — Day-0 triage (the first 30 minutes)
The goal of the first 30 minutes is orientation, not findings. Build a mental model of the system. Findings come later.
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.
- 9d ago First seen · 419 lines · 93 tokens per session scan A ce57183c39ed
codebase-audit is a skill published in the GitHub repository GoldenWing-360/claude-security-skills (17 stars, last pushed 1mo ago), licensed MIT. It adds 93 tokens to every session and 4,759 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 2 findings (makes network calls, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
spark-engineer
Use when writing Spark jobs, debugging performance issues, or configuring cluster settings for Apache Spark applications, distributed data processing pipelines, or big data workloads. Invoke to write DataFrame transformations, optimize Spark SQL queries, implement RDD pipelines, tune shuffle operations, configure…
debugging-wizard
Parses error messages, traces execution flow through stack traces, correlates log entries to identify failure points, and applies systematic hypothesis-driven methodology to isolate and resolve bugs. Use when investigating errors, analyzing stack traces, finding root causes of unexpected behavior, troubleshooting…
log-analyzer
A log-analysis helper that reads application and system logs to find unusual patterns and likely causes. Logs are records of events such as errors, requests, warnings, and service activity.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
Reverse Engineering & Binary Analysis
Binary analysis, assembly interpretation, disassembly, decompilation, firmware RE, and protocol reverse engineering.