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/undeadlist/claude-code-agents/full-auditnpx skills add undeadlist/claude-code-agents --skill full-auditgit clone --depth 1 https://github.com/undeadlist/claude-code-agentsWrote 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/undeadlist/claude-code-agents/full-audit)<a href="https://agentmods.dev/skills/undeadlist/claude-code-agents/full-audit"><img src="https://agentmods.dev/badge/skills/undeadlist/claude-code-agents/full-audit.svg" alt="Measured on agentmods" 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 | $0.00020 | $0.00521 |
| Opus 5 | $0.00010 | $0.00260 |
| Sonnet 5 | $0.00004 | $0.00104 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
full-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 4d 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
Full Audit Workflow
Run a comprehensive audit of the entire codebase. Use before major releases or as a weekly health check.
Phase 1: Parallel Audit
Spawn ALL of the following agents in parallel (single response with multiple Task calls):
| Agent | Output File | Focus |
|---|---|---|
code-auditor |
.claude/audits/AUDIT_CODE.md |
Code quality |
bug-auditor |
.claude/audits/AUDIT_BUGS.md |
Runtime bugs |
security-auditor |
.claude/audits/AUDIT_SECURITY.md |
OWASP deep scan |
doc-auditor |
.claude/audits/AUDIT_DOCS.md |
Documentation gaps |
infra-auditor |
.claude/audits/AUDIT_INFRA.md |
Infrastructure config |
ui-auditor |
.claude/audits/AUDIT_UI_UX.md |
UI/UX and accessibility |
db-auditor |
.claude/audits/AUDIT_DB.md |
Database performance |
perf-auditor |
.claude/audits/AUDIT_PERF.md |
Performance issues |
dep-auditor |
.claude/audits/AUDIT_DEPS.md |
Dependency health |
seo-auditor |
.claude/audits/AUDIT_SEO.md |
SEO optimization |
api-tester |
.claude/audits/API_TEST_REPORT.md |
API validation |
Each agent targets the project's source code. Provide each with a prompt like:
Audit [target directory]. Save report to [output file].
Phase 2: Consolidation
After all auditors complete, spawn:
fix-planner- Read all.claude/audits/AUDIT_*.mdfiles and create.claude/audits/FIXES.mdwith prioritized action items
Post-Audit Actions
- Review
FIXES.md- Prioritize based on your timeline - Run
code-fixer- Implement P1 (critical) fixes - Run
test-runner- Verify fixes work - Re-audit affected areas if needed
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.
- 4d ago First seen · 44 lines · 20 tokens per session scan A d32dd38afb14
full-audit is a skill published in the GitHub repository undeadlist/claude-code-agents (147 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 521 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…