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 ravindrakele/claude-skills --skill deep-security-auditgit clone --depth 1 https://github.com/ravindrakele/claude-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/ravindrakele/claude-skills/deep-security-audit)<a href="https://agentmods.dev/skills/ravindrakele/claude-skills/deep-security-audit"><img src="https://agentmods.dev/badge/skills/ravindrakele/claude-skills/deep-security-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/ravindrakele/claude-skills/deep-security-audit"><img src="https://agentmods.dev/badge/skills/ravindrakele/claude-skills/deep-security-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.00174 | $0.01745 |
| Opus 5 | $0.00087 | $0.00873 |
| Sonnet 5 | $0.00035 | $0.00349 |
| Haiku 4.5 | $0.00017 | $0.00175 |
Grade A, and why
deep-security-audit 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 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.
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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deep Security Audit
A repeatable, multi-agent pipeline that finds real, exploitable security bugs by understanding code, not pattern-matching. It fans work out to scoped finder agents, then makes a second wave of agents try to refute each finding before it's reported — so what survives is high-signal.
Operating rules (non-negotiable)
- READ-ONLY. Static analysis of source only. Never edit/commit/push. Never run an exploit against a live/hosted system. Local, self-owned, non-destructive PoCs only — and only if the user explicitly asks to verify one.
- Understand, don't grep. grep is for locating the surface. Every finding must come from an agent that read the handler, its callers, its auth/middleware/validation, and traced reachability. No finding from a raw grep hit alone.
- Prove the guard is ABSENT. A missing check is only a finding if you
verified the framework's normal guard (nonce, capability, policy,
permission_callback, auth middleware,prepare(), escaping, validation) is genuinely not there on that path. Frameworks have defaults — check them. - Honest CVSS, no inflation. Score CVSS 3.1 by real preconditions. If a
BOLA needs an unguessable UUID →
AC:H. If exploitation needs auth →PR:L/H. State the precondition. Downgrade the moment evidence contradicts the ceiling. - Empirically calibrate when possible. If a "read-back / exfil" claim can be safely checked locally and the data doesn't actually come back (lossy AI/serializer layer, blind SSRF), downgrade it — don't report the theoretical worst case as confirmed.
- Local ≠ deployed. The checkout may lag or lead production. Flag that
findings are "candidates to verify against the deployed branch," and diff
against
origin/the deploy branch when possible. - No false positives from non-runtime code. Ignore tests, stubs, fixtures,
seeders, factories,
*.min.js, vendor/, node_modules/, and env examples.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 119 lines · 174 tokens per session scan A d0bde22111e9
deep-security-audit is a skill published in the GitHub repository ravindrakele/claude-skills (3 stars, last pushed 1mo ago), licensed MIT. It adds 174 tokens to every session and 1,745 once invoked, about $0.0009 per session on Opus 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-08-31.
Other skills, from other repositories
binary-crypto-verify
Verifies in compiled machine code that security properties survived the compiler: that secret zeroization was not removed by dead-store elimination and that constant-time logic did not regain secret-dependent branches. Use when auditing a binary, shared object, static library, or firmware image whose source claims…
codebase-security-audit
Audits a codebase, module, or single file for exploitable vulnerabilities across injection, authentication and authorization, secrets management, memory safety, deserialization, SSRF, and dependency risk, gating every candidate through reachability and impact review before reporting. Use when asked to security-audit…
crypto-source-audit
Audits cryptographic source code for timing side channels, missing secret zeroization, non-constant-time comparison, and weak randomness. Use when reviewing crypto primitives, key/nonce/PSK handling, TLS or handshake code, signature or KEM implementations, or any function that touches secret key material, including…
meta-tags-optimizer
Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate. Generates multiple A/B test variations with character counting and SERP preview. Use when asked to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "fix my meta tags", "social media…
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
sxo
Search Experience Optimization (SXO) — the bridge between SEO and UX/CRO. Audits the full journey from the SERP click to the on-page goal: SERP click-through factors (title/meta/rich results that win the click), then post-click experience signals that keep users and drive conversions — above-the-fold relevance and…