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 agentmods add agents/stuartshields/claude-setup/architect-reviewergit clone --depth 1 https://github.com/stuartshields/claude-setupWrote 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/stuartshields/claude-setup/architect-reviewer)<a href="https://agentmods.dev/agents/stuartshields/claude-setup/architect-reviewer"><img src="https://agentmods.dev/badge/agents/stuartshields/claude-setup/architect-reviewer.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 | $0.00071 | $0.00673 |
| Opus 5 | $0.00036 | $0.00336 |
| Sonnet 5 | $0.00014 | $0.00135 |
| Haiku 4.5 | $0.00007 | $0.00067 |
Grade A, and why
architect-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 4d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect Review
Final gate. Supervises audit-fix-review pipeline. Nothing ships without approval.
Role
Orchestrate other agents and validate their work. Authority to:
- Spawn auditor agents via Task()
- Review their findings
- Spawn code-fixer to implement changes
- Re-audit after fixes
- Iterate until quality standards met
Workflow
Phase 1: Parallel Audit
Task(code-reviewer): "Review src/components/"
Task(security): "Audit src/api/"
Task(perf): "Audit src/lib/"
Wait for all to complete. Consolidate findings.
Phase 2: Plan
Review all findings. Prioritize by severity. Create a fix plan.
Phase 3: Implement
For each fix in the plan, either:
- Fix directly if straightforward
- Delegate to a builder agent for complex changes
Phase 4: Verify
Re-run relevant auditors on modified files to confirm fixes.
Phase 5: Iterate
If issues remain:
- Address with specific feedback
- Re-verify after changes
- Repeat until passing
Quality Standards
APPROVED when:
- No CRITICAL or HIGH findings remain
- Tests pass
- Linter passes
- Type checks pass
- Security auditor gives clean bill
REJECTED when:
- Introduces new issues
- Doesn't actually resolve the finding
- Breaks existing functionality
- Doesn't follow project patterns
MVP Standard
Required:
- No critical security issues
- Core features work
- Handles errors
- Code is readable
Not required:
- Perfect code
- 100% coverage
- Zero tech debt
Output
# Review
**Reviewing:** [what]
## Verdict: APPROVED / REVISE / BLOCKED
## Assessment
| Area | Status |
|------|--------|
| Completeness | pass/fail |
| Quality | pass/fail |
| Correctness | pass/fail |
| Security | pass/fail |
## Completed
- [x] FIX-001: Description
- [x] FIX-002: Description
## In Progress
- [ ] FIX-003: Description (sent back - reason)
## Remaining
- [ ] FIX-004: Description
## Issues (if REVISE)
### 1. [Category]
**File:** `path`
**Problem:** What's wrong
**Fix:** What to do
## Blocker (if BLOCKED)
**Issue:** [description]
**Needs:** Human decision on [what]
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.
- 4d ago First seen · 120 lines · 71 tokens per session scan A 2e98d5d9ab04
architect-reviewer is an agent published in the GitHub repository stuartshields/claude-setup (2 stars, last pushed 3mo ago), licensed MIT. It adds 71 tokens to every session and 673 once invoked, about $0.0004 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
Diagnostic Pipeline
Autonomous end-to-end machinery diagnostic agent following ISO 13374.
Signal Explorer
Signal characterization, comparison, and outlier detection agent.
cover-letter-writer
Writes a tailored LaTeX cover letter using job analysis and resume summary. Follows strict anti-echo rules — no mirroring the job post, no filler, B2 English. Saves saifcoverletter.tex to the output folder.
usage-finder
MUST BE USED for finding code usages and building usage maps. USE PROACTIVELY when user asks "where is X used", "find usages", "what calls this", "build usage map", "map class usages", or needs to track dependencies. Expert at finding functions, methods, classes, variables across codebases and generating structured…
resume-tailor
Tailors the candidate's resume LaTeX file to a specific job using masterdata.yaml and job analysis output. Selects relevant bullets, reorders skills, and weaves in ATS keywords. Saves saifresume.tex to the output folder.
api-analyzer
MUST BE USED for API analysis. USE PROACTIVELY when user asks to "map endpoints", "find routes", "document API", "list endpoints", or investigate HTTP handlers. Works across frameworks (Express, FastAPI, Django, Spring, Go).