xmcp is a TypeScript framework for building applications with the Model Context Protocol, a standard for connecting AI models with tools and external context. Developers use it to create MCP-based integrations.
Borrowing it
Nothing to install: this file belongs to basementstudio/xmcp. 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/basementstudio/xmcp/main/.claude/commands/review-rules.mdgit clone --depth 1 https://github.com/basementstudio/xmcpWrote 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/commands/basementstudio/xmcp/review-rules)<a href="https://agentmods.dev/commands/basementstudio/xmcp/review-rules"><img src="https://agentmods.dev/badge/commands/basementstudio/xmcp/review-rules/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/commands/basementstudio/xmcp/review-rules"><img src="https://agentmods.dev/badge/commands/basementstudio/xmcp/review-rules.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.00009 | $0.00209 |
| Opus 5.5 | $0.00004 | $0.00084 |
| Sonnet 5.5 | $0.00002 | $0.00042 |
| Haiku 4.5 | $0.00001 | $0.00021 |
Grade A, and why
review-rules 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.
What it actually says
Run a rule-by-rule review of the current working tree against the tracked agent guidance and review standards.
Do this:
- Read
AGENTS.md, the applicable scopedAGENTS.mdfiles, andREVIEW_RULES.md. - Gather the diff:
git diff HEADgit diff --cachedgit status --short
- For each relevant standard, produce:
- Rule name:
pass|fail|n/a - If
fail: cite the specificfile:line, quote the offending code, and suggest the concrete fix. - If
n/a: one short sentence on why it does not apply to this diff.
- Rule name:
- End with a Summary listing only failing rules, ordered by severity: structural/design issues first, then mechanical issues.
Do not modify files during the review. Output only.
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 · 25 lines · 9 tokens per session scan A b6afa3bb6136
review-rules is a command published in the GitHub repository basementstudio/xmcp (1,342 stars, last pushed today), licensed MIT. It adds 9 tokens to every session and 209 once invoked, about $0.0000 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-30.
Other commands, from other repositories
code-review
Review code for bugs, improvements, and best practices with actionable feedback.
devkit.typescript.code-review
Provides comprehensive TypeScript monorepo code review for Nx workspaces including NestJS backend, React web, and React Native mobile apps. Use when reviewing architecture, boundaries, security, performance, CI/CD and Nx-specific practices.
pr-ready
Run the project's pre-commit review loop to determine whether the current branch is ready to push — lint, tests, parallel pr-review-toolkit agents plus an over-engineering audit, fix-and-re-run until convergence.
review-code
Read ALL memory bank code rules + best practices, check the files that changed, and APPLY fixes so they adhere. The active counterpart to /scan (which is read-only). Use after an AI session, before commit, to make changed files compliant.
pre-pr
Run the full pre-PR gate (pnpm all) and self-review the diff against the component checklist.
pn-audit-data
Design or review database schema — normalization, indexing strategy, migration plan, and data model decisions. Surgical command for database design. Use standalone or as part of pn-backend-audit.