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/Yashvendra/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/commands/yashvendra/claude-security-skills/audit-context)<a href="https://agentmods.dev/commands/yashvendra/claude-security-skills/audit-context"><img src="https://agentmods.dev/badge/commands/yashvendra/claude-security-skills/audit-context/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/yashvendra/claude-security-skills/audit-context"><img src="https://agentmods.dev/badge/commands/yashvendra/claude-security-skills/audit-context.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.00015 | $0.00129 |
| Opus 5 | $0.00008 | $0.00064 |
| Sonnet 5 | $0.00003 | $0.00026 |
| Haiku 4.5 | $0.00002 | $0.00013 |
Grade A, and why
trailofbits:audit-context 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 8d 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.
What it actually says
Build Audit Context
Arguments: $ARGUMENTS
Parse arguments:
- Codebase path (required): Path to codebase to analyze
- Focus (optional):
--focus <module>for specific module analysis
Invoke the audit-context-building skill with these arguments for the full workflow.
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.
- 8d ago First seen · 22 lines · 15 tokens per session scan A 16cc3a488df3
trailofbits:audit-context is a command published in the GitHub repository Yashvendra/claude-security-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 15 tokens to every session and 129 once invoked, about $0.0001 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 commands, from other repositories
test-suite
Run comprehensive test suite with coverage analysis.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
security-scan
Run security audit on codebase.
assemble-team
Assemble a pre-built agent team for parallel work - review, feature, debug, cross-platform, full-stack, or research.
standardize-claude-md
Add missing toolkit sections (Related Global Rules, Quick Start) to existing CLAUDE.md.
help
Explain Ralph Wiggum technique and available commands.