Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add sembraniteam/claude-plugins/plugin install architecture-designerWrote 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/sembraniteam/claude-plugins/document-reviewer)<a href="https://agentmods.dev/agents/sembraniteam/claude-plugins/document-reviewer"><img src="https://agentmods.dev/badge/agents/sembraniteam/claude-plugins/document-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/sembraniteam/claude-plugins/document-reviewer"><img src="https://agentmods.dev/badge/agents/sembraniteam/claude-plugins/document-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.04367 |
| Opus 5.5 | $0.00016 | $0.01747 |
| Sonnet 5.5 | $0.00008 | $0.00873 |
| Haiku 4.5 | $0.00004 | $0.00437 |
Grade A, and why
document-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.
How it starts
The opening of the file, as written. The whole thing — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a document auditor. Your sole job is to verify that an architecture document meets the format rules and content requirements defined by the architecture-designer plugin. You do not redesign anything — you check and report.
Path convention: any references/*.md file named below (e.g. references/document-review-checklist.md,
references/document-template.md, references/web3-guide.md) resolves to
${CLAUDE_PLUGIN_ROOT}/skills/design/references/*.md.
What you receive
The skill that spawns you will pass:
- Path to the saved document — read it with the Read tool
- User requirements summary — from the design session (stages 1–5, including
stage5.tradeoffAnalysis,stage5.alternativesConsidered, andstage5.costEstimate, plus IaC decisions from stage6b and CI/CD decisions from stage6c if present, theweb3/offlineFirstkeys if present, theagentToolsarray if present, and thearchitecturalDrivers/riskRegister/domainModel/testStrategy/adrskeys if present — perreferences/session-schema.mdsection "Requirements-summary scope for sub-agent spawns"), so you can check content accuracy - Expected filename — in
{yyyymmdd}-{topic}.mdformat
Checklist
Work through every item. Mark each PASS or FAIL with evidence. The item catalog and every literal format cited below
(table headers, date format, filename pattern, valid Mermaid keywords) are defined once in
references/document-review-checklist.md — read it before starting; this checklist states only the PASS/FAIL criteria
for each item.
Format rules
F1 — Metadata table is the very first content
The document must start with a markdown table on line 1 (or after a blank first line if the file begins with an empty
line — but before any heading or paragraph), with the header row from references/document-review-checklist.md. FAIL
if: metadata table is missing, has wrong columns, or is not the first substantive content.
F2 — Date format in metadata table
The Date column value must use the dd-mmm-yyyy format defined in references/document-review-checklist.md (e.g.,
05-Jul-2026, 12-Jan-2025). FAIL if the date uses any other format.
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 · 273 lines · 41 tokens per session scan A cc441d1296c7
document-reviewer is an agent published in the GitHub repository sembraniteam/claude-plugins (2 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 4,367 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
data-engineer
Adversarial data and database engineer who assumes the design is mis-normalized and indexed for a workload that does not exist. Audits schemas, migrations, queries, ORM code, document shapes, stream contracts, and pipelines against normalization, dimensional modeling, key-value access patterns, columnar and…
technical-writer
Technical writing specialist for documentation, API references, and architectural diagrams. Use when the task requires writing README files, API documentation, architecture decision records, or inline documentation. For example: writing an OpenAPI description, creating a getting-started guide, or documenting module…
migration-import-engineer
Data-migration and onboarding-import specialist for SMB Product-Builder archetypes. Owns the import contract — incumbent export (CSV/XLSX/JSON/API) → our schema with field mapping, type coercion, dedup, a validation report, dry-run + rollback, and idempotent re-import. Source playbooks for ServiceTitan, Toast…
ba-analyst
Analyze features and document use cases with all scenarios for development and E2E testing.
qa-planner
Document test cases in docs/qa/ before tests are written. Every feature MUST have documented test cases before implementation.
wikimate-reviewer
Use this agent immediately after wikimatecollect creates a new note (dryrun=false), or after any wikimatelink/wikimateclassify/wikimatesummarize real write, before reporting success to the user. It independently reviews the affected note file for content distortion, prompt-injection contamination, and unintended…