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 issuegit 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/issue)<a href="https://agentmods.dev/skills/jhlee0409/all-for-claudecode/issue"><img src="https://agentmods.dev/badge/skills/jhlee0409/all-for-claudecode/issue.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.00019 | $0.01717 |
| Opus 5 | $0.00010 | $0.00859 |
| Sonnet 5 | $0.00004 | $0.00343 |
| Haiku 4.5 | $0.00002 | $0.00172 |
Grade A, and why
afc:issue 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.
How it starts
The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/afc:issue — GitHub Issue Analysis
Analyzes a single GitHub issue (title, body, labels, comments, attached images) and produces a structured analysis document. Searches the codebase for related files and suggests the appropriate next afc skill (debug, spec, or auto).
Pre-fetch
!gh --version >/dev/null 2>&1 && gh auth status >/dev/null 2>&1 && echo "GH_OK" || echo "GH_UNAVAILABLE"
Arguments
$ARGUMENTS— (required) One of:- Issue number:
123or#123 - GitHub URL:
https://github.com/owner/repo/issues/123 - Cross-repo:
owner/repo#123
- Issue number:
Execution Steps
1. Prerequisites Check
If the pre-fetch returned GH_UNAVAILABLE:
- Output:
[afc:issue] Error: GitHub CLI (gh) is not installed or not authenticated. Install from https://cli.github.com/ and run 'gh auth login'. - Abort immediately.
2. Parse Input
Determine the input format and extract owner, repo, and issue number:
- GitHub URL (
https://github.com/{owner}/{repo}/issues/{number}): extract from path, setGH_REPO_FLAG="--repo {owner}/{repo}" - Cross-repo (
{owner}/{repo}#{number}): split on#, setGH_REPO_FLAG="--repo {owner}/{repo}" - Local number (
123or#123): strip leading#, setGH_REPO_FLAG=""(use current repo from git remote)
3. Collect Issue Data
gh issue view {number} {GH_REPO_FLAG} --json number,title,body,labels,author,comments,createdAt,state,url
If the command fails → output error and abort.
Parse and extract: TITLE, BODY, LABELS, AUTHOR, COMMENTS, CREATED_AT, STATE, URL.
4. Analyze Attached Images
Extract image URLs from the issue body (skip images inside code block fences):
- Markdown:
 - HTML:
<img src="{url}">
For each URL: fetch with WebFetch, analyze content (error messages, UI screenshots, console output, stack traces), tag results with [Image Analysis]. Record failures as [Image unavailable: {url}].
If no images: note No attached media found.
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 · 192 lines · 19 tokens per session scan A d3d9354f5639
afc:issue is a skill published in the GitHub repository jhlee0409/all-for-claudecode (7 stars, last pushed 5mo ago), licensed MIT. It adds 19 tokens to every session and 1,717 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
check-cache-bugs
Audit Claude Code setup for cache bugs (CC#40524): sentinel, --resume/--continue, attribution header + ArkNill B3/B4/B5.
investigate
Systematic root-cause debugging: find the cause before writing any fix.
sandbox-unblock
Diagnostic protocol to run before reporting a sandbox blocker or asking for a configuration change. Eight checks that eliminate false positives, then a report template the person holding the settings can act on. On one measured day, six of eight reported blockers turned out to be false, all from the same handful of…
qa
Systematic QA testing of a web application: diff-aware, tiered, with fix-and-verify loop.
optimize
Analyze and suggest performance improvements for code, queries, or systems.
debug-systematic
Systematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, race conditions, or unexplained failures.