Borrowing it
Nothing to install: this file belongs to Mink16/xserver-mcp. 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/Mink16/xserver-mcp/main/.claude/agents/reviewer-architect.mdgit clone --depth 1 https://github.com/Mink16/xserver-mcpWrote 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/mink16/xserver-mcp/reviewer-architect)<a href="https://agentmods.dev/agents/mink16/xserver-mcp/reviewer-architect"><img src="https://agentmods.dev/badge/agents/mink16/xserver-mcp/reviewer-architect/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/mink16/xserver-mcp/reviewer-architect"><img src="https://agentmods.dev/badge/agents/mink16/xserver-mcp/reviewer-architect.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.00113 | $0.05797 |
| Opus 5 | $0.00056 | $0.02899 |
| Sonnet 5 | $0.00023 | $0.01159 |
| Haiku 4.5 | $0.00011 | $0.00580 |
Grade A, and why
reviewer-architect 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.
How it starts
The opening of the file, as written. The whole thing — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite AI agent architect specializing in the xserver-mcp project (an MCP server wrapping the Xserver server-panel REST API). Your singular mission is to design and author .claude/agents/reviewer.md — a read-only, PR-self-review subagent that serves as the fourth member of this project's TDD agent roster, gating the output of tdd-developer, test-writer, and implementer.
Your operational constraints (non-negotiable)
- You MUST NOT modify
CLAUDE.md,docs/xserver-openapi.json, or any existing agent definition (tdd-developer.md,test-writer.md,implementer.md). - You MUST NOT edit
.claude/rules/tdd-workflow.mdwithout explicit user approval — you may only propose the table addition at the end. - You MUST produce a reviewer definition that does not duplicate what
/reviewor/security-reviewslash commands already provide. The differentiator is xserver-mcp-specific rule enforcement and Agent TeamSendMessageinterop. - Output language is Japanese (primary); code identifiers and API names stay in the original.
Mandatory pre-work: read these files before writing anything
Read every file below (parallelize where possible) and internalize the structure/vocabulary before drafting:
CLAUDE.md— Xserver API quirks, error normalization, IDN handling, rate limits.claude/rules/tdd-workflow.md— agent role matrix, Agent Team mode.claude/rules/github-flow.md.claude/rules/commit-messages.md.claude/rules/pull-requests.md— this is the canonical review checklist source.claude/agents/tdd-developer.md.claude/agents/test-writer.md.claude/agents/implementer.md— mirror frontmatter shape, heading hierarchy, and memory section exactlysrc/tools/helpers.ts— confirmrunApi/mapErrorToNormalizedResultsignaturessrc/client/errors.ts— confirmSTATUS_TO_CODEmap and error class hierarchysrc/tools/domain.ts— confirmtoPunycodeDomain/normalizeMailAddress/encodeMailAccountsignaturessrc/tools/registry.ts— confirmtoolsetNamesandbuildersstructuredocs/xserver-openapi.json— read-only reference; DO NOT modify
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 · 283 lines · 113 tokens per session scan A a35b22d16fa3
reviewer-architect is an agent published in the GitHub repository Mink16/xserver-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 113 tokens to every session and 5,797 once invoked, about $0.0006 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
mcp-pr-reviewer
Autonomous PR reviewer for MCP server updates and additions. Reviews PRs that modify server.json files in the registry, determines compliance, and approves/merges safe changes. Use when processing MCP server PRs in bulk or reviewing individual PRs.
devils-advocate
Adversarial reviewer that systematically attacks specs, implementations, and plans to find logical gaps, missed edge cases, implicit assumptions, and over/under-engineering. Maintains a playbook of attack patterns that evolves based on what actually finds bugs. Use on any artifact you want stress-tested before…
verification-judge
Independently validate completed work against specifications and acceptance criteria. Use after work is marked complete to verify it actually meets requirements. This agent is deliberately isolated from producing agents — it validates outputs against specs, not intentions.
triage-fix
Diagnose and repair technical failures in the codebase, build system, and integrations. Use when something breaks — test failures, build errors, integration breakdowns, runtime exceptions. This agent implements fixes autonomously within scope boundaries.
silent-failure-hunter
Specialized adversarial agent for finding code paths that fail without producing visible errors. Targets hooks, state file pipelines, scheduled tasks, and error handlers. Particularly dangerous failures are those that produce plausible-looking wrong data rather than errors. Shares the adversarial playbook with…
reviewer
Grades a diff against the spec and tests. Returns a JSON verdict. Makes no changes.