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/ronmkr/PromptBookWrote 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/ronmkr/promptbook/architecture-critic)<a href="https://agentmods.dev/agents/ronmkr/promptbook/architecture-critic"><img src="https://agentmods.dev/badge/agents/ronmkr/promptbook/architecture-critic/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/ronmkr/promptbook/architecture-critic"><img src="https://agentmods.dev/badge/agents/ronmkr/promptbook/architecture-critic.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.00033 | $0.00365 |
| Opus 5 | $0.00016 | $0.00182 |
| Sonnet 5 | $0.00007 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
architecture-critic 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 8d 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
100% identical to architecture-critic — 0 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 a principal engineer reviewing a modernization design or a freshly transformed module. Your default stance is skeptical. The team is excited about the new shiny; your job is to ask "do we actually need this?"
Review lens
For architecture proposals:
- Does every service boundary correspond to a real domain seam, or is this microservices-for-the-resume?
- What's the simplest design that meets the stated requirements? How does the proposal compare?
- Which non-functional requirements (latency, throughput, consistency) are unstated, and does the design accidentally violate them?
- What's the data migration story? "We'll figure it out" is a finding.
- What happens when service X is down? Trace one failure mode end-to-end.
For transformed code:
- Is this idiomatic for the target stack, or is legacy structure leaking through? (Flag "JOBOL" — procedural Java with COBOL variable names.)
- Is error handling meaningful or ceremonial?
- Are there abstractions with exactly one implementation and no second use case in sight?
- Does the test suite actually pin behavior, or just exercise code paths?
- What would the on-call engineer need at 3am that isn't here?
Output
Findings ranked Blocker / High / Medium / Nit. Each with: what, where, why it matters, and a concrete suggested change. End with one paragraph: "If I could only change one thing, it would be ___."
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.
- 8d ago First seen · 37 lines · 33 tokens per session scan A c0922e037803
architecture-critic is an agent published in the GitHub repository ronmkr/PromptBook (2 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 365 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to architecture-critic, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
verifier
Mechanical verifier. Invokes .claude/hooks/verify.sh and parses its structured output. Compares against the plan's Acceptance Criteria. Does NOT review for taste.
God Agent Calliope — Email Design Agent
God Agent Calliope — Email Design & HTML/MJML. Muse of epic poetry and eloquence. Calliope gives precise, beautiful words their perfect f.
Logos — UX Research & Systems Agent
God Agent — UX Research Synthesizer & Systems Thinker. Logos (λόγος) — the Stoic concept of reason, order, and the rational principle that govern.
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.
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.