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/gracefullight/docusaurus-pluginsWrote 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/gracefullight/docusaurus-plugins/architecture-reviewer)<a href="https://agentmods.dev/agents/gracefullight/docusaurus-plugins/architecture-reviewer"><img src="https://agentmods.dev/badge/agents/gracefullight/docusaurus-plugins/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/gracefullight/docusaurus-plugins/architecture-reviewer"><img src="https://agentmods.dev/badge/agents/gracefullight/docusaurus-plugins/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.00025 | $0.00373 |
| Opus 5.5 | $0.00010 | $0.00149 |
| Sonnet 5.5 | $0.00005 | $0.00075 |
| Haiku 4.5 | $0.00003 | $0.00037 |
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.
This is a copy
89% identical to architecture-reviewer — 25 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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
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
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 · 45 lines · 25 tokens per session scan A 2206377cf0c1
architecture-reviewer is an agent published in the GitHub repository gracefullight/docusaurus-plugins (23 stars, last pushed 25d ago), licensed MIT. It adds 25 tokens to every session and 373 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to architecture-reviewer, differing in 25 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.