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 jhlee0409/all-for-claudecode --skill securitygit clone --depth 1 https://github.com/jhlee0409/all-for-claudecodeWrote 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/jhlee0409/all-for-claudecode/security)<a href="https://agentmods.dev/skills/jhlee0409/all-for-claudecode/security"><img src="https://agentmods.dev/badge/skills/jhlee0409/all-for-claudecode/security.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.1 | $0.00013 | $0.01413 |
| Opus 5 | $0.00006 | $0.00707 |
| Sonnet 5 | $0.00003 | $0.00283 |
| Haiku 4.5 | $0.00001 | $0.00141 |
Grade A, and why
afc:security 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 7d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/afc:security — Security Scan
Detects and reports security vulnerabilities in the codebase. Inspects against OWASP Top 10. Read-only — does not modify code.
Arguments
$ARGUMENTS— (optional) scan scope (file/directory path, or "full" for full scan)- If not specified: scans only files changed in the current branch
Config Load
Architecture, Code Style, and Project Context are auto-loaded via .claude/rules/afc-project.md.
Read .claude/afc.config.md if CI commands are needed.
If neither rules file nor config exists: read CLAUDE.md for framework info. Assume "unknown" if no source has it.
For dependency audit command: infer from packageManager field in package.json or the lockfile (e.g., npm audit, yarn audit, pnpm audit).
Execution Steps
1. Determine Scan Scope
$ARGUMENTS= path → that path only$ARGUMENTS= "full" → entire codebase- Not specified → changed files from:
!
git diff --name-only HEAD 2>/dev/null || echo "[GIT_DIFF_FAILED]"
2. Agent Teams (when scan complexity warrants it)
Use Agent Teams when the scan scope is complex enough that a single-pass review would miss cross-file vulnerability patterns. Assess holistically:
- File types: Auth handlers, trust boundary code, and input-processing layers warrant deeper multi-agent scrutiny than config files or simple utilities
- Code volume: Large files with dense logic benefit from focused agent attention
- Diversity of concerns: Multiple distinct security domains (auth + injection + data exposure) across separate modules
- Trust boundaries: Files that cross privilege levels (user input → DB, client → server, public → internal API)
Use Agent Teams when any of the following apply:
- Scan includes auth handlers, session management, or access control logic spanning multiple files
- Input entry points and their sanitization/consumption code live in different directories
- The scope spans multiple distinct security domains that cannot be assessed in a single coherent pass
What ships with it
1 file 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.
- 7d ago First seen · 165 lines · 13 tokens per session scan A d876a32dfff8
afc:security is a skill published in the GitHub repository jhlee0409/all-for-claudecode (7 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 1,413 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 skills, from other repositories
eval-agents
Audit Claude Code agents defined in .claude/agents/ for description specificity, model tier appropriateness, tools scoping, and system prompt quality. Detects dispatch ambiguity between agents, flags over-permissive tool grants, and checks for human-in-the-loop patterns that break programmatic orchestration. Use when…
orchestrator-lanes
A file-based project-management playbook for a specific Claude Code development orchestrator. It organizes work into lanes, plans, dependency steps, validation phases, and shipping stages.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
self-assessment
Interactive skill assessment with personalized learning path generation.
git-ai-archaeology
Analyze AI config evolution in a git repo. Use when mapping AI adoption history, finding when configs were first introduced, charting commit velocity by month, or identifying maturity phases in a project's AI tooling.
source-command-methodology-advisor
Analyzes your codebase and asks 3 targeted questions to recommend the right AI-assisted development methodology stack.