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 launchgit 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/launch)<a href="https://agentmods.dev/skills/jhlee0409/all-for-claudecode/launch"><img src="https://agentmods.dev/badge/skills/jhlee0409/all-for-claudecode/launch.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.00017 | $0.01715 |
| Opus 5 | $0.00009 | $0.00857 |
| Sonnet 5 | $0.00003 | $0.00343 |
| Haiku 4.5 | $0.00002 | $0.00171 |
Grade A, and why
afc:launch 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/afc:launch — Generate Release Artifacts
Generates release artifacts (CHANGELOG entry, README updates, GitHub Release notes) from git history and optional spec context. This is a standalone utility — not part of the auto pipeline. Works with or without a prior afc pipeline run.
Arguments
$ARGUMENTS— (optional) One of:- Version tag: e.g.
"v2.2.1"— uses this as the release version "auto"— auto-detects version from package.json/Cargo.toml/pyproject.toml- Not specified: prompts for version
- Version tag: e.g.
Git Context (auto-loaded)
!git describe --tags --abbrev=0 2>/dev/null || echo "[NO_TAGS]"
!git log $(git describe --tags --abbrev=0 2>/dev/null || echo "")..HEAD --pretty=format:"%h %s" --no-merges 2>/dev/null || git log --pretty=format:"%h %s" --no-merges
Execution Steps
1. Detect Project Context
-
Version detection:
- If
$ARGUMENTSis a version string (matchesv?\d+\.\d+\.\d+): use it - If
$ARGUMENTS="auto": read version from package.json → Cargo.toml → pyproject.toml → setup.py (first found) - If not specified: check package.json etc. for current version, present to user, confirm or override
- If
-
Previous version detection:
git describe --tags --abbrev=0 2>/dev/null || echo "none"- If a previous tag exists: diff range =
{previous_tag}..HEAD - If no tags: diff range = all commits (warn user: "No previous release tag found. Including all history.")
- If a previous tag exists: diff range =
-
Changelog detection:
- Check for existing:
CHANGELOG.md→CHANGES.md→HISTORY.md - If found: will prepend new entry
- If not found: will create
CHANGELOG.md
- Check for existing:
2. Gather Change Context
Collect all available context for high-quality release notes:
-
Git history (required):
git log {previous_tag}..HEAD --pretty=format:"%h %s" --no-merges -
Changed files summary (required):
git diff --stat {previous_tag}..HEAD -
Spec context (optional — enhances quality):
- Glob
.claude/afc/specs/*/spec.md— if any exist, read Overview and User Stories sections - This provides intent context that raw commit messages lack
- If no specs found: rely on git history only (still produces good output)
- Glob
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 · 187 lines · 17 tokens per session scan A b467163bc504
afc:launch is a skill published in the GitHub repository jhlee0409/all-for-claudecode (7 stars, last pushed 5mo ago), licensed MIT. It adds 17 tokens to every session and 1,715 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
pr-triage
4-phase PR backlog management with audit, deep code review, validated comments, and optional worktree setup. Use when triaging pull requests, catching up on pending code reviews, or managing a backlog of open PRs. Args: 'all' to review all, PR numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit…
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
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.
review-pr
Perform a comprehensive code review of a pull request.
git-worktree-clean
Clean up stale git worktrees with merged branch detection and disk usage report.
release-notes-generator
Generate release notes in 3 formats (CHANGELOG.md, PR body, Slack announcement) from git commits. Automatically categorizes changes and converts technical language to user-friendly messaging. Use for releases, changelogs, version notes, what's new summaries, or ship announcements.