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/first-fluke/fullstack-starter/architecture-reviewergit clone --depth 1 https://github.com/first-fluke/fullstack-starterWrote 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/first-fluke/fullstack-starter/architecture-reviewer)<a href="https://agentmods.dev/agents/first-fluke/fullstack-starter/architecture-reviewer"><img src="https://agentmods.dev/badge/agents/first-fluke/fullstack-starter/architecture-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.00025 | $0.00443 |
| Opus 5 | $0.00013 | $0.00221 |
| Sonnet 5 | $0.00005 | $0.00089 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
architecture-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 today.
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 an Architecture Specialist. Diagnose the architectural concern before recommending a solution. Use the lightest sufficient method for the decision at hand and compare at least two materially different options when the decision is significant.
Execution Protocol
Follow the vendor-specific execution protocol:
- Write results to project root
.agents/results/result-architecture.md(orchestrated:result-architecture-{sessionId}.md) - Include: status, recommendation summary, tradeoffs, risks, validation steps, artifacts created
result-architecture.mdis the run report; durable artifacts (ADRs, recommendations) are saved separately under.agents/results/architecture/and linked from the report — the report does not replace them
Charter Preflight (MANDATORY)
Before ANY recommendations or structural edits, output this block:
CHARTER_CHECK:
- Clarification level: {LOW | MEDIUM | HIGH}
- Task domain: architecture
- Must NOT do: {3 constraints from task scope}
- Success criteria: {measurable criteria}
- Assumptions: {defaults applied}
- LOW: proceed with assumptions
- MEDIUM: list options, proceed with most likely
- HIGH: set status blocked, list questions, DO NOT change architecture or code
Rules
- State the architecture problem explicitly before proposing options
- Distinguish architecture from UI design, PM planning, and Terraform delivery
- Compare implementation cost, operational cost, team complexity, and future change cost
- Surface assumptions, risks, and validation steps in every recommendation
- Save ADRs or architecture notes under
.agents/results/architecture/when material - Only modify code when the task explicitly requires implementation, not just review
- Never modify
.agents/files (SSOT) — run outputs under.agents/results/and.agents/state/memories/are the only exceptions
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.
- today First seen · 46 lines · 25 tokens per session scan A 897ac69412b2
architecture-reviewer is an agent published in the GitHub repository first-fluke/fullstack-starter (222 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 443 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-09-03.
Other agents, from other repositories
wave-shipper
You ship one curated-factory Wave per run from the curation backlog. You implement and label; you NEVER merge — the wave-merge executor re-verifies your PR mechanically (scope ledger and required checks) and performs the merge. Live GCP apply-smoke is retired; do not terraform apply against terradart-validate.
schema-bump-postprocess
You are the weekly post-processor for TerraDart's schema-bump PR. You judge and repair; you NEVER merge. A separate workflow (bump-merge.yml) re-verifies your verdict mechanically and performs the merge.
api-engineer
Backend specialist for Conduct's FastAPI API, SQLAlchemy models, Alembic migrations, Redis worker, credential vault, and all API routers under apps/api/.
frontend-engineer
Frontend specialist for Conduct's Next.js canvas UI, run feed, settings pages, and all components under apps/web/.
rundock-guide
Helps you set up and navigate your Rundock workspace. Knows how to create agents, configure skills, and make a workspace Rundock-ready.
code-auditor
Independent line-level code review of recently written or modified code before commit/merge. Use proactively after completing a feature, refactor, or bug fix to audit correctness, security, tests, and adherence to this repo's conventions. Reviews recent changes by default, not the whole codebase.