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 architectgit 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/architect)<a href="https://agentmods.dev/skills/jhlee0409/all-for-claudecode/architect"><img src="https://agentmods.dev/badge/skills/jhlee0409/all-for-claudecode/architect/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/architect"><img src="https://agentmods.dev/badge/skills/jhlee0409/all-for-claudecode/architect.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.00010 | $0.01189 |
| Opus 5 | $0.00005 | $0.00594 |
| Sonnet 5 | $0.00002 | $0.00238 |
| Haiku 4.5 | $0.00001 | $0.00119 |
Grade A, and why
afc:architect 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/afc:architect — Architecture Analysis and Design Advice
Analyzes the codebase architecture and records design decisions. Ensures design quality through convergence-based Critic Loop. Does not modify source code. May write ADR files to
.claude/afc/memory/decisions/.
Arguments
$ARGUMENTS— (required) analysis target or design question (e.g., "review state management strategy", "where to add new entity")
Config Load
Read .claude/afc.config.md if CI commands are needed.
Architecture, Code Style, and Project Context are auto-loaded via .claude/rules/afc-project.md.
If neither rules file nor config exists: read CLAUDE.md for architecture info. Assume "Layered Architecture" if no source has it.
Execution Steps
1. Determine Scope
Analyze $ARGUMENTS to identify the task type:
| Type | Example | Output |
|---|---|---|
| Structure Analysis | "timeline module structure" | Dependency map + improvement suggestions |
| Design Question | "where to put new feature?" | Placement suggestion + rationale |
| ADR Recording | "Redis vs In-memory decision" | Architecture Decision Record |
| Refactoring Evaluation | "need to split store?" | Current issues + refactoring plan |
2. Explore Codebase
- Explore relevant directories/files (Glob, Grep, Read)
- Trace dependency flow (import relationships)
- Verify {config.architecture} structure
- Identify existing patterns
Use Agent Teams for wide analysis scope (3+ modules) with parallel exploration:
Task("analyze features/timeline", subagent_type: "Explore")
Task("analyze widgets/timeline", subagent_type: "Explore")
Cross-Module Import Chain Verification (after Explore agents return):
When parallel Explore agents are used, the orchestrator must verify cross-module boundaries that no single agent can see:
- From each agent's dependency map, extract outbound imports that cross module boundaries
- For each cross-module import chain (e.g., widget → feature → shared), read the actual import statements at the boundary files
- Verify against {config.architecture} rules: does the full chain respect layer direction, not just each module's internal imports?
- Report any cross-module violations not surfaced by individual agents
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 · 142 lines · 10 tokens per session scan A 13820016624a
afc:architect is a skill published in the GitHub repository jhlee0409/all-for-claudecode (7 stars, last pushed 5mo ago), licensed MIT. It adds 10 tokens to every session and 1,189 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
audit-agents-skills
Audit Claude Code agents, skills, and commands for quality and production readiness. Use when evaluating skill quality, checking production readiness scores, or comparing agents against best-practice templates.
design-patterns
Detect, suggest, and evaluate GoF design patterns in TypeScript/JavaScript codebases. Use when refactoring code, applying singleton/factory/observer/strategy patterns, reviewing pattern quality, or finding stack-native alternatives for React, Angular, NestJS, and Vue.
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…
eval-skills
Audit all skills in the current project for frontmatter completeness, effort level appropriateness, allowed-tools scoping, and content quality. Produces a scored report with effort-level recommendations for each skill. Use when onboarding to a new project, reviewing skill quality before shipping, or adding effort…
eval-rules
Audit .claude/rules/ files for structural correctness, glob validity, and real-world usefulness. Resolves each paths: pattern against actual project files, then asks the user whether each rule is still relevant and useful. Can update rules in-place based on answers. Use when setting up rules for the first time…
review-pr
Perform a comprehensive code review of a pull request.