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 consultgit 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/consult)<a href="https://agentmods.dev/skills/jhlee0409/all-for-claudecode/consult"><img src="https://agentmods.dev/badge/skills/jhlee0409/all-for-claudecode/consult/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jhlee0409/all-for-claudecode/consult"><img src="https://agentmods.dev/badge/skills/jhlee0409/all-for-claudecode/consult.svg" alt="Reviewed on agentmods" width="80" 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.00023 | $0.01418 |
| Opus 5 | $0.00012 | $0.00709 |
| Sonnet 5 | $0.00005 | $0.00284 |
| Haiku 4.5 | $0.00002 | $0.00142 |
Grade A, and why
afc:consult 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 9d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/afc:consult — Expert Consultation
Consult a domain expert for advice tailored to your project. Each expert has persistent memory — they remember your project's decisions across sessions. Pipeline-independent: works anytime, no active pipeline required.
Arguments
$ARGUMENTS— (optional) Format:[domain] "[question]" [brief|deep]domain— one of:backend,infra,pm,design,marketing,legal,security,advisor,peer(optional, auto-detected if omitted)question— the consultation question (optional, enters exploratory mode if omitted)brief|deep— depth hint (optional, default:auto)
Execution Steps
1. Parse Arguments
Extract from $ARGUMENTS:
- domain: first word if it matches a known domain name
- question: remaining text after domain (if any), with quotes stripped
- depth: last word if it matches
briefordeep
If $ARGUMENTS is empty → go to Step 2 (domain selection).
2. Domain Detection
A. Explicit domain provided → use it directly.
B. No domain, but question provided → intent-based evaluation:
| Domain | When to route |
|---|---|
| backend | Server-side logic, data modeling, API design, authentication flows, database decisions |
| infra | Deployment, CI/CD pipelines, cloud services, scaling, reliability, monitoring |
| pm | What to build, for whom, when, how to measure success, prioritization, scope |
| design | Visual hierarchy, interaction patterns, accessibility, component design, user flow |
| marketing | SEO, content strategy, acquisition funnels, analytics tracking, growth tactics |
| legal | Regulatory obligations, license compatibility, privacy requirements |
| security | Threats, vulnerabilities, attack surfaces, threat modeling, compliance |
| advisor | Choosing between technologies, frameworks, libraries, or architectural approaches |
| peer | Think through a problem collaboratively, explore directions, weigh trade-offs |
Identify the PRIMARY expertise gap — what specialized knowledge does the user need most?
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.
- 9d ago First seen · 147 lines · 23 tokens per session scan A 8402dce5600e
afc:consult is a skill published in the GitHub repository jhlee0409/all-for-claudecode (7 stars, last pushed 5mo ago), licensed MIT. It adds 23 tokens to every session and 1,418 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
authentication-patterns
OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.
contract-redliner
Contract review, redlining, and negotiation support with clause analysis, risk identification, and markup templates. Use when reviewing contracts, identifying unfavorable terms, suggesting amendments, or preparing negotiation positions.
email-systems
Transactional email (Resend, SendGrid, SES), templates (React Email, MJML), deliverability (SPF/DKIM/DMARC), and inboxing best practices. Use when building email infrastructure, designing templates, or troubleshooting deliverability.
event-driven-architecture
Kafka, RabbitMQ, SQS/SNS, event sourcing, CQRS, saga patterns, dead letter queues, and idempotency. Use when designing asynchronous systems, implementing message-driven workflows, or building event streaming pipelines.
graphql-expert
GraphQL API design and implementation. Use when building GraphQL APIs, designing schemas, implementing resolvers, or optimizing GraphQL performance.
ai-policy-generator
AI governance policy creation for nonprofits and enterprises with frameworks, risk assessment, ethical guidelines, and compliance templates. Use when drafting AI usage policies, responsible AI frameworks, or organizational AI governance documents.