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 initgit 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/init)<a href="https://agentmods.dev/skills/jhlee0409/all-for-claudecode/init"><img src="https://agentmods.dev/badge/skills/jhlee0409/all-for-claudecode/init.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.00011 | $0.01461 |
| Opus 5 | $0.00005 | $0.00731 |
| Sonnet 5 | $0.00002 | $0.00292 |
| Haiku 4.5 | $0.00001 | $0.00146 |
Grade A, and why
afc:init 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/afc:init — Project Initial Setup
Creates project-local configuration files (
.claude/afc.config.md,.claude/rules/afc-project.md,.claude/afc/project-profile.md). Project-local only — never touches~/.claude/CLAUDE.md. For global routing setup use/afc:setup.
Project State (auto-loaded)
!ls .claude/afc.config.md .claude/rules/afc-project.md .claude/selfish.config.md .claude/.selfish-* 2>/dev/null | head -20 || echo "[no existing afc files]"
Arguments
$ARGUMENTS— (optional) additional context or hints for project analysis
Execution Steps
1. Legacy Migration (v1.x → v2.x)
Detect and migrate selfish-pipeline artifacts in one pass:
.claude/selfish.config.mdexists,afc.config.mddoes not → rename toafc.config.md.claude/.selfish-*files found → rename each to.afc-{x}.claude/selfish/exists,.claude/afc/does not → rename to.claude/afc/git tag -l 'selfish/*'→ rename known patterns toafc/equivalent, delete the rest
Print a single migration summary line. If nothing to migrate, skip silently.
2. Check for Existing Config
If .claude/afc.config.md already exists and this is NOT a migration:
- Ask user: "Config file already exists. Overwrite?"
- If declined: abort
3. Analyze Project Structure
Use $ARGUMENTS as additional context. Detection heuristics are in reference.md — consult it for package manager, framework, architecture, and tool detection tables.
- Read
package.json→ extract CI scripts, detect package manager from lockfile - Detect framework from
package.jsondeps - Detect architecture from directory structure +
tsconfig.jsonpaths - Detect state/styling/testing/linter/DB tools
- Read 2–3 code samples to verify naming patterns
Detection is best-effort. Present results to user for confirmation before writing files.
4. Generate Config File
Write .claude/afc.config.md based on template at ${CLAUDE_SKILL_DIR}/../../templates/afc.config.template.md:
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 · 141 lines · 11 tokens per session scan A ccbe60143392
afc:init is a skill published in the GitHub repository jhlee0409/all-for-claudecode (7 stars, last pushed 5mo ago), licensed MIT. It adds 11 tokens to every session and 1,461 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
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…