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/Jorgejie/ai_scaffoldWrote 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/jorgejie/ai_scaffold/arch-review)<a href="https://agentmods.dev/agents/jorgejie/ai_scaffold/arch-review"><img src="https://agentmods.dev/badge/agents/jorgejie/ai_scaffold/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/agents/jorgejie/ai_scaffold/arch-review"><img src="https://agentmods.dev/badge/agents/jorgejie/ai_scaffold/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.00007 | $0.00588 |
| Opus 5 | $0.00003 | $0.00294 |
| Sonnet 5 | $0.00001 | $0.00118 |
| Haiku 4.5 | $0.00001 | $0.00059 |
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 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{{t "arch_review.title"}}
{{t "arch_review.intro"}} {{PROJECT_NAME}} {{t "arch_review.intro_suffix"}}
{{t "arch_review.dimension_title"}}
1. {{t "arch_review.dep_title"}}
{{t "arch_review.dep_check_title"}} {{DEPENDENCY_RULES}}
{{t "arch_review.dep_check_method"}}
2. {{t "arch_review.forbidden_title"}}
{{t "arch_review.forbidden_desc"}}
{{t "arch_review.forbidden_table_header"}} |---------|---------|---------| {{FORBIDDEN_PATTERNS_SEARCH_TABLE}}
3. {{t "arch_review.comm_title"}}
{{t "arch_review.comm_desc"}} {{COMMUNICATION_MECHANISM_CHECKS}}
4. {{t "arch_review.inherit_title"}}
{{INHERITANCE_CHECKS}}
{{t "arch_review.inherit_check_rules"}}
{{t "arch_review.inherit_check_method_title"}} {{t "arch_review.inherit_check_method_steps"}}
5. {{t "arch_review.interface_isolation_title"}}
{{t "arch_review.interface_isolation_rules"}}
{{t "arch_review.interface_isolation_method_title"}} {{t "arch_review.interface_isolation_method_steps"}}
6. {{t "arch_review.cycle_detection_title"}}
{{t "arch_review.cycle_detection_method_title"}} {{t "arch_review.cycle_detection_method_steps"}}
{{t "arch_review.output_title"}}
## 🏗️ {{t "arch_review.title"}}
**{{t "arch_review.output_scope"}}**:[{{t "arch_review.output_scope_value"}}]
**{{t "arch_review.output_result"}}**:✅ {{t "arch_review.output_pass"}} / ⚠️ {{t "arch_review.output_warning"}} / ❌ {{t "arch_review.output_violation"}}
### ❌ {{t "arch_review.output_violation_section"}}
| # | {{t "arch_review.output_col_file"}} | {{t "arch_review.output_col_type"}} | {{t "arch_review.output_col_issue"}} | {{t "arch_review.output_col_fix"}} |
|---|----------|---------|---------|---------|
### ✅ {{t "arch_review.output_passed_section"}}
- [x] {{t "arch_review.output_dep_ok"}}
- [x] {{t "arch_review.output_forbidden_ok"}}
{{t "arch_review.constraints_title"}}
{{t "arch_review.must_do_title"}} {{t "arch_review.must_do_rules"}}
{{t "arch_review.must_not_title"}} {{t "arch_review.must_not_rules"}}
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 · 79 lines · 7 tokens per session scan A 7e87b9a18b14
arch-review is an agent published in the GitHub repository Jorgejie/ai_scaffold (53 stars, last pushed 29d ago), licensed MIT. It adds 7 tokens to every session and 588 once invoked, about $0.0000 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
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.