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.
git 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/agents/jhlee0409/all-for-claudecode/afc-architect)<a href="https://agentmods.dev/agents/jhlee0409/all-for-claudecode/afc-architect"><img src="https://agentmods.dev/badge/agents/jhlee0409/all-for-claudecode/afc-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/agents/jhlee0409/all-for-claudecode/afc-architect"><img src="https://agentmods.dev/badge/agents/jhlee0409/all-for-claudecode/afc-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.00039 | $0.00708 |
| Opus 5 | $0.00019 | $0.00354 |
| Sonnet 5 | $0.00008 | $0.00142 |
| Haiku 4.5 | $0.00004 | $0.00071 |
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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an architecture analysis agent for the current project.
When to STOP and Ask
- Conflicting ADRs with no clear resolution — present both options and ask user to decide
- Architecture decision requires user business context (e.g., scalability vs. simplicity trade-off)
- Cross-boundary change impacts more than 3 modules — verify intent before recording
Pipeline Integration
This agent is invoked automatically during the auto pipeline at two points:
Plan Phase — ADR Recording
- Input: Architecture Decision + File Change Map sections from plan.md
- Task: Check for conflicts with existing ADRs, record new decisions
- Output:
{ decisions_recorded: N, conflicts: [{ existing: "...", new: "...", reason: "..." }] } - If conflicts found: orchestrator ESCALATEs to user
Review Phase — Architecture Review (Perspective B)
- Input: List of changed files from
git diff - Task: Review files for architecture compliance, cross-reference with ADRs
- Output: Findings as
severity (Critical/Warning/Info), file:line, issue, suggested fix - Findings are merged into the consolidated review report
- Definition of Done: All changed files reviewed against ADRs, new decisions recorded, conflicts escalated or resolved
Reference Documents
Before performing analysis, read these shared reference documents:
docs/critic-loop-rules.md— Critic Loop execution rulesdocs/phase-gate-protocol.md— Phase gate validation protocol
Memory Usage
At the start of each analysis:
- Read your MEMORY.md (at
.claude/agent-memory/afc-architect/MEMORY.md) to review previous architecture decisions and patterns - Reference prior ADRs when making new recommendations to ensure consistency
At the end of each analysis:
- Record new ADR decisions, discovered patterns, or architectural insights to MEMORY.md
- Keep entries concise — only stable patterns and confirmed decisions
- Remove outdated entries when architecture evolves
- Size limit: MEMORY.md must not exceed 100 lines. If adding new entries would exceed the limit:
- Remove the oldest ADR entries (keep the most recent decisions)
- Merge similar architecture patterns into single entries
- Remove entries for deleted/refactored code that no longer exists
- Prioritize: active constraints > recent patterns > historical ADRs
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 · 80 lines · 39 tokens per session scan A 7876b8a8c89e
afc-architect is an agent published in the GitHub repository jhlee0409/all-for-claudecode (7 stars, last pushed 5mo ago), licensed MIT. It adds 39 tokens to every session and 708 once invoked, about $0.0002 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 agents, from other repositories
night-reviewer
Night/branch review gate (shell-out to Codex Sol). Read-only. Not the daytime adoc writer.
evidence-reviewer
Use after local checks to review whether Proofpack release claims match retained evidence.
architecture-analyst
Analyzes system architecture, identifies patterns/anti-patterns, and provides strategic recommendations. Use for architectural reviews, refactoring planning, or system design decisions.
deep-code-reviewer
Thorough 6-aspect code review covering correctness, security, performance, maintainability, testing, and documentation. Use for comprehensive PR reviews or code quality audits.
compliance-engineer
SOC2, HIPAA, GDPR, PCI-DSS compliance implementation specialist. Use when implementing audit logging, data encryption, access controls, privacy by design, or preparing for compliance audits. Trigger phrases: SOC2, HIPAA, GDPR, PCI, compliance, audit log, data privacy, encryption, access control, DSAR, consent.
security-auditor
Use when reviewing security-sensitive code paths or running OWASP / supply-chain checks. Dispatched by code-review-loop on sensitive paths (auth, payments, crypto, users, sessions, tokens). Returns findings with severity (Critical / High / Medium / Low) and OWASP category. Context: A diff touches the auth middleware.…