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/jhlee0409/all-for-claudecode/setupnpx skills add jhlee0409/all-for-claudecode --skill setupgit 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/setup)<a href="https://agentmods.dev/skills/jhlee0409/all-for-claudecode/setup"><img src="https://agentmods.dev/badge/skills/jhlee0409/all-for-claudecode/setup.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.00016 | $0.01941 |
| Opus 5 | $0.00008 | $0.00971 |
| Sonnet 5 | $0.00003 | $0.00388 |
| Haiku 4.5 | $0.00002 | $0.00194 |
Grade B, and why
afc:setup scanned grade B with 1 finding 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 6d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
!`cat ~/.claude/CLAUDE.md 2>/dev/null || echo "[CLAUDE.md NOT FOUND]"` How it starts
The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/afc:setup — Global CLAUDE.md Configuration
Manages the all-for-claudecode routing block in
~/.claude/CLAUDE.md. Global only — modifies~/.claude/CLAUDE.md, not project files. For project-local setup, use/afc:init.
Current State
!cat ~/.claude/CLAUDE.md 2>/dev/null || echo "[CLAUDE.md NOT FOUND]"
Arguments
--force— skip conflict prompts, default to coexistence mode
Steps
1. Version Resolution
Read ${CLAUDE_SKILL_DIR}/../../package.json → extract "version" → use as {PLUGIN_VERSION}.
2. Analyze Current State
Parse the pre-fetched CLAUDE.md content above:
<!-- AFC:START -->found → existing AFC block- Extract
<!-- AFC:VERSION:X.Y.Z -->. If matches{PLUGIN_VERSION}: printAFC block already up to date (v{PLUGIN_VERSION})and stop. - Otherwise: replace block in Step 5.
- Extract
<!-- SELFISH:START -->found → remove entireSELFISH:START…SELFISH:ENDblock, printRemoved legacy SELFISH block, proceed.- Neither → fresh install, proceed to Step 5.
3. Conflict Scan
Detect conflicts in unguarded content (outside any <!-- *:START/END --> blocks).
See conflict-detection.md for marker-block algorithm and conflict keyword table.
Skip this step if --force is set — default to coexistence.
4. Resolve Conflicts
No conflicts → proceed to Step 5.
Conflicts found — show scan summary and ask:
CLAUDE.md Scan Results
├─ Tool blocks found: {names} (lines {range})
├─ Agent routing conflicts: {count} — e.g. "executor" (line XX) ↔ afc:implement
└─ Skill routing conflicts: {count}
"Directives overlapping with afc were found. Choose resolution:"
- afc-exclusive — add override rules inside the AFC block (does not touch other tools' blocks)
- coexistence — append AFC block as-is (end-of-file position gives it priority)
- manual cleanup — print conflict list and abort
- Option 3: print list and abort without writing.
5. Inject AFC Block
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.
- 6d ago First seen · 171 lines · 16 tokens per session scan B 0a2db42690a9
afc:setup is a skill published in the GitHub repository jhlee0409/all-for-claudecode (7 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 1,941 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
hns-lsel-curator
Local Self-Evolution Loop (LSEL) curator — the CLUSTER + drain engine for the GOOS-local PROPOSE→APPLY seam closure (SPEC-LSEL-LOCAL-EVOLUTION-001). Companion-offset drain of .moai/lessons-inbox.jsonl with a drain-side severity filter that drops the 65% Bash-timeout/sandbox noise, eventkey clustering with a frequency…
moai-workflow-worktree
Git worktree management for parallel SPEC development with isolated workspaces, automatic branch registration, and seamless MoAI-ADK integration. Use when setting up parallel development environments.
hns-workflow-ci-loop
Unified CI watch + auto-fix loop skill. Polls gh pr checks after /moai sync PR creation, classifies required vs auxiliary failures, attempts safe automated patches (max 3 iterations), and escalates semantic failures to the user. Use for CI loop workflow — NOT for general loop iteration patterns (see…
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…
moai-harness-learner
Harness learning subsystem coordinator. Produces Tier 4 auto-update proposal payloads consumed by the orchestrator (which surfaces them via AskUserQuestion) and orchestrates Apply/Rollback flows. Triggers when harness learning proposals are pending or learning lifecycle management is needed.
hns-oss-docs-readme-sync
README 4-file synchronization procedure for the oss-docs harness: Korean README.ko.md as primary source, en/ja/zh derivation, the shared language-switcher header contract, section-order parity checklist, and the manual verification recipe (no linter exists for READMEs). Loaded by the content-author and…