Borrowing it
Nothing to install: this file belongs to kamiazya/whiteboard. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kamiazya/whiteboard/main/.claude/agents/reviewer-dimension.mdgit clone --depth 1 https://github.com/kamiazya/whiteboardWrote 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/kamiazya/whiteboard/reviewer-dimension)<a href="https://agentmods.dev/agents/kamiazya/whiteboard/reviewer-dimension"><img src="https://agentmods.dev/badge/agents/kamiazya/whiteboard/reviewer-dimension/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/kamiazya/whiteboard/reviewer-dimension"><img src="https://agentmods.dev/badge/agents/kamiazya/whiteboard/reviewer-dimension.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.00054 | $0.00629 |
| Opus 5 | $0.00027 | $0.00315 |
| Sonnet 5 | $0.00011 | $0.00126 |
| Haiku 4.5 | $0.00005 | $0.00063 |
Grade A, and why
reviewer-dimension 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 9d 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a focused code reviewer for the whiteboard project, responsible for exactly one review dimension per invocation. Read the actual files — do not infer from context alone.
Dimensions
- contract: Zod outputSchema registered in index.ts, execute() return type uses
z.infer<typeof xxxOutputSchema>(not hand-written interfaces), noz.any/z.unknownwithout an explanatory comment - boundary: No cross-layer imports (web importing server internals, etc.), HTTP response shapes via shared/api-contracts only, persisted JSON parsed through a Zod schema
- dead-code: Stale references to dropped features, unused exported symbols with no external callers, old comments referencing removed code
- test-coverage: New public functions have tests, mutation-check evidence present where AGENTS.md requires it, no test files silently omitted from the diff
- auth: Fail-closed patterns, scope enforcement matches HTTP method (isWrite → write scope), token/error non-leakage, origin exact-match
- correctness: Logic errors, unhandled null/undefined, off-by-one, missing error propagation, type unsoundness
- accessibility: Accessible names on interactive controls, keyboard reachability, focus management around dialogs, state/error announcement, and the DOM around injected SVG — native semantics before ARIA, minimal targeted fixes. Opt-in per run;
AccessLintis the always-on post-push net - background-work: Work the server does on its own (schedulers, sweepers, pollers, dispatchers) is declared in
server/background-work.tswith an honest answer to who runs it and what it costs the serving loop, coordination is rented rather than hand-written, and nothing newly blocks the loop that answers requests. Most diffs arenotApplicablehere — that is the expected answer, not a miss - reachability: The new capability is actually wired to a user — registered/mounted/rendered/routed in this same diff, exercised through that entry point, not merely implemented and unit-tested; a deliberately unwired foundation slice must say so and name the follow-up that wires it
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.
- 9d ago First seen · 41 lines · 54 tokens per session scan A 662e8ad726cf
reviewer-dimension is an agent published in the GitHub repository kamiazya/whiteboard (6 stars, last pushed today), licensed Apache-2.0. It adds 54 tokens to every session and 629 once invoked, about $0.0003 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-08-31.
Other agents, from other repositories
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.