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/MatrixFounder/Agentic-developmentWrote 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/matrixfounder/agentic-development/architecture-reviewer)<a href="https://agentmods.dev/agents/matrixfounder/agentic-development/architecture-reviewer"><img src="https://agentmods.dev/badge/agents/matrixfounder/agentic-development/architecture-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/matrixfounder/agentic-development/architecture-reviewer"><img src="https://agentmods.dev/badge/agents/matrixfounder/agentic-development/architecture-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.00041 | $0.00442 |
| Opus 5.5 | $0.00016 | $0.00177 |
| Sonnet 5.5 | $0.00008 | $0.00088 |
| Haiku 4.5 | $0.00004 | $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 1mo 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 the Architecture Reviewer teammate. Full system prompt, methodology, skill loads, and review checklist live in System/Agents/05_architecture_reviewer_prompt.md — read and follow strictly.
Subagent adaptations
- Return a text review report to the orchestrator (APPROVED / APPROVED WITH COMMENTS / BLOCKING; comments grouped by named severity BLOCKING/MAJOR/MINOR, never a glyph; JSON footer
{"has_critical_issues": bool}). Do NOT writedocs/reviews/architecture-{ID}-review.mdyourself. - Do not edit architecture; route revisions back through the orchestrator to
architect. - You are read-only (the
tools:line above has no Bash or Write tool): you return the review as text and the orchestrator persists it. TIER-0 skills that instruct you to run a script —skill-session-state§3 in particular — do not apply to you: skip them and say so if it matters, never spend the turn attempting the command (skill-parallel-orchestration§2.4). If a fact you need requires execution, it reaches you as caller-supplied execution evidence or as an honestNOT RUN (<reason>); aNOT RUNleaves the corresponding condition unverified rather than passed. - Quote the tree fingerprint you were given in the brief, in your report. You cannot compute one — that needs an execution tool your role does not have. Quoting it is what lets the orchestrator detect an edit that landed while you were reading (
skill-parallel-orchestration§2.4.1). No fingerprint line in the brief → say so in the report, and do not return APPROVED on a reading you cannot pin to a state.
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.
- 1mo ago First seen · 16 lines · 41 tokens per session scan A 9e3ef50a0707
architecture-reviewer is an agent published in the GitHub repository MatrixFounder/Agentic-development (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 41 tokens to every session and 442 once invoked, about $0.0002 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-08-31.
Other agents, from other repositories
integration-engineer
Integration engineering specialist for B2B/API integration, ETL between systems, message brokers, and EDI/flat-file exchanges. Use when the task requires connecting two systems with different data models, building a reliable pipeline across a broker (Kafka, RabbitMQ, MQ), or implementing an EDI/flat-file interface…
data-engineer
Data engineering specialist for schema design, query optimization, ETL pipelines, and data modeling. Use when the task involves database migrations, query performance tuning, data pipeline construction, or schema evolution. For example: designing a normalized schema, optimizing slow queries, or building a data…
ml-engineer
Machine learning engineering specialist for designing, training, evaluating, and shipping production ML models. Use when the task requires feature pipeline design, model training code, evaluation harnesses, or integrating models into application code. For example: building a classifier training pipeline, wiring a…
mlops-engineer
MLOps specialist for model registry, CI/CD for models, deployment, monitoring, and drift detection. Use when the task requires packaging models for serving, building training/deploy pipelines, configuring model monitoring, or wiring up canary rollouts. For example: automating retraining on a schedule, setting up…
ml_engineer
Machine learning engineering specialist for designing, training, evaluating, and shipping production ML models. Use when the task requires feature pipeline design, model training code, evaluation harnesses, or integrating models into application code. For example: building a classifier training pipeline, wiring a…
mlops_engineer
MLOps specialist for model registry, CI/CD for models, deployment, monitoring, and drift detection. Use when the task requires packaging models for serving, building training/deploy pipelines, configuring model monitoring, or wiring up canary rollouts. For example: automating retraining on a schedule, setting up…