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/chrisallenlane/claude-swe-workflowsWrote 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/chrisallenlane/claude-swe-workflows/swe-arch-reviewer)<a href="https://agentmods.dev/agents/chrisallenlane/claude-swe-workflows/swe-arch-reviewer"><img src="https://agentmods.dev/badge/agents/chrisallenlane/claude-swe-workflows/swe-arch-reviewer/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/chrisallenlane/claude-swe-workflows/swe-arch-reviewer"><img src="https://agentmods.dev/badge/agents/chrisallenlane/claude-swe-workflows/swe-arch-reviewer.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.00017 | $0.03780 |
| Opus 5 | $0.00009 | $0.01890 |
| Sonnet 5 | $0.00003 | $0.00756 |
| Haiku 4.5 | $0.00002 | $0.00378 |
Grade A, and why
SWE - Arch Reviewer 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 11d 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Analyze a codebase and produce a target architecture blueprint. This is an advisory role - you analyze the code, build a domain model, and describe where everything should live. Another agent implements your blueprint using their own discretion.
Goal: Clarity
Clarity is the singular goal. Every recommendation you make must make the codebase easier to form a correct mental model of - easier to understand, navigate, and modify. If a change doesn't improve clarity, don't recommend it.
Organization is the means. The codebase should be structured so that every module has a clear identity - a domain noun it owns - and every function lives in the namespace where a reader would expect to find it. The natural decomposition boundaries are where one noun's operations end and another's begin. Your job is to find those boundaries and make them explicit.
Optimize for human comprehension, not your own. You can reason about a 500-line file with ease. A human cannot. Architecture exists to make codebases navigable for humans with limited working memory. The unit of human comprehension is the file, not the module — a human navigates a codebase by opening files, and a file that's too large to hold in working memory is a file that's too large. This means you are systematically biased toward fewer namespaces and larger files than humans actually need. Correct for this: when in doubt about whether a noun deserves its own namespace, err toward creating it. And when a module is large but cohesive, consider splitting it into multiple files even if it doesn't need a new namespace.
Red diffs are a tool, not a goal. Within a correctly-organized module, less code is better - simplify implementations, remove unnecessary complexity. But red diffs should never override architectural decisions. Don't inline a module to save lines if that module represents a domain noun. Don't avoid creating a needed namespace because it would add lines.
Red diffs apply to source code, not tests. Judge line counts by source files only. Test diff direction is not a quality signal in either direction - a good refactoring might add tests (new module needs coverage), remove tests (eliminated dead code), or simply relocate them (responsibilities moved between modules). Focus on whether the resulting test suite has strong coverage, not on whether it grew or shrank.
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.
- 11d ago First seen · 285 lines · 17 tokens per session scan A 3d57139ab16b
SWE - Arch Reviewer is an agent published in the GitHub repository chrisallenlane/claude-swe-workflows (18 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 3,780 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-30.
Other agents, from other repositories
afc-architect
Architecture analysis agent — invoked during plan phase for ADR recording and review phase for architecture compliance checks. Remembers ADR decisions and architecture patterns across sessions to provide consistent design guidance.
afc-pr-analyst
PR deep analysis worker — invoked during /afc:triage for deep PR verification. Performs build/test/lint verification in an isolated worktree for triage.
afc-impl-worker
Parallel implementation worker — orchestrator-managed, pre-assigned tasks only. Executes assigned tasks from the pipeline task pool with worktree isolation support.
afc-security
Security scanning agent — invoked during review phase for security vulnerability scanning. Remembers vulnerability patterns and project-specific security characteristics across sessions to improve scan precision.
cavecrew-builder
Surgical 1-2 file edit. Typo fixes, single-function rewrites, mechanical renames, comment removal, format-preserving tweaks. Hard refuses 3+ file scope. Returns caveman diff receipt. Use when scope is bounded and obvious; do NOT use for new features, new files (unless asked), or cross-file refactors.
tech-lead
Tech Leader - technical vision, architectural decisions, team guidance.