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/10Legs/freelance-developer-harnessWrote 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/commands/10legs/freelance-developer-harness/arch-review)<a href="https://agentmods.dev/commands/10legs/freelance-developer-harness/arch-review"><img src="https://agentmods.dev/badge/commands/10legs/freelance-developer-harness/arch-review/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/commands/10legs/freelance-developer-harness/arch-review"><img src="https://agentmods.dev/badge/commands/10legs/freelance-developer-harness/arch-review.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.00008 | $0.00259 |
| Opus 5.5 | $0.00003 | $0.00104 |
| Sonnet 5.5 | $0.00002 | $0.00052 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
arch-review 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 5d 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.
What it actually says
You are running an Architecture Review for: $ARGUMENTS
Review Checklist
Solution Architect evaluates:
Pattern Compliance
- Does this follow established patterns in
patterns/architecture/? - If new pattern, has it been documented?
- Are there reusable patterns being duplicated unnecessarily?
Design Principles
- Is this the simplest design that meets requirements?
- Is it designed for change (extensible)?
- Are all decisions documented?
Security
- Has Security Reviewer been consulted for security-sensitive decisions?
- Are there any obvious security concerns?
Scalability
- Does this design hold under 10x current expected load?
- Are there single points of failure?
ADR Requirement
- Have all significant decisions been recorded as ADRs?
Verdict
- APPROVED — Implementation may proceed
- APPROVED WITH CONDITIONS — Implementation may proceed after addressing listed conditions
- BLOCKED — Fundamental redesign needed (specific issues listed)
Output
Document review at:
clients/{{CLIENT_SLUG}}/specs/arch-review-{{date}}.md
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.
- 5d ago First seen · 41 lines · 8 tokens per session scan A ac31201ab8e2
arch-review is a command published in the GitHub repository 10Legs/freelance-developer-harness (33 stars, last pushed 1mo ago), licensed MIT. It adds 8 tokens to every session and 259 once invoked, about $0.0000 per session on Opus 5.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-10-02.
Other commands, from other repositories
sessions
Use aiwg sessions to manage the normalized session catalog, imports, analytics, and authorized forensic evidence with versioned JSON.
help
Quick reference for all Attune commands.
guide
Interactive guide to fellowship. Walks you through a real task using the structured research-plan-implement flow, then shows you what's next.
chronicle
One-time codebase onboarding — interactively extracts your team's conventions, identifies reference files, and generates CLAUDE.md sections so Claude codes the way your team does. Run once per project.
scribe
Create a reusable quest template for a specific type of task (e.g., "API endpoint", "migration"). Encodes project-specific rules and conventions into phase guidance that loads automatically during quests.
spec
Spec-driven development — brainstorm, plan, review, and execute with quality gates and approval.