Borrowing it
Nothing to install: this file belongs to mort-lab/excel-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/mort-lab/excel-mcp/main/.claude/commands/prp-core/prp-core-review.mdgit clone --depth 1 https://github.com/mort-lab/excel-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/commands/mort-lab/excel-mcp/prp-core-review)<a href="https://agentmods.dev/commands/mort-lab/excel-mcp/prp-core-review"><img src="https://agentmods.dev/badge/commands/mort-lab/excel-mcp/prp-core-review.svg" alt="Measured on agentmods" 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.00000 | $0.00617 |
| Opus 5 | $0.00000 | $0.00309 |
| Sonnet 5 | $0.00000 | $0.00123 |
| Haiku 4.5 | $0.00000 | $0.00062 |
Grade A, and why
prp-core-review 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
94% identical to review-general — 186 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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review
Please perform a comprehensive code review of the current changes or specified files.
Review Scope
Scope for review $1 Link to must read PRP file if prp was used for implemnetaiton (skip if this is empty) $2
Review Process
- Understand Changes
- If reviewing staged changes:
git diff --staged - If reviewing specific files: Read the specified files
- If reviewing a PR:
gh pr view --json files,additions,deletions - If reviewing a local directory:
git diff - If reviewing the entire codebase:
git diff origin/main
- If reviewing staged changes:
Review Focus Areas
-
Code Quality
- Type hints on all functions and classes
- Pydantic v2 models for data validation
- No print() statements (use logging)
- Proper error handling
- Following PEP 8
- Docstrings following google style python docstrings
-
Pydantic v2 Patterns
- Using ConfigDict not class Config
- field_validator not @validator
- model_dump() not dict()
- Proper use of Annotated types
-
Security
- Input validation on all endpoints
- No SQL injection vulnerabilities
- Passwords properly hashed
- No hardcoded secrets
-
Structure
- Unit tests are co-located with the code they test in tests/ folders
- Each feature is self-contained with its own models, service, and tools
- Shared components are only things used by multiple features
- Future improvements (like multiple AI providers) would go in src/shared/ai_providers/ when implemented
- Integration tests remain at the root level in tests/integration/
-
Linting
- ruff check --fix
- mypy
-
Testing
- New code has tests
- Edge cases covered
- Mocking external dependencies
-
Performance
- No N+1 queries
- Efficient algorithms
- Proper async usage
-
Documentation
- Clear README with setup instructions
- CLAUDE.md is up to date with any new important utils, dependencies etc for future cluade code instances
Review Output
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 · 94 lines · 0 tokens per session scan A 872a3e5f8b5b
prp-core-review is a command published in the GitHub repository mort-lab/excel-mcp (5 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 617 tokens. A static security scan graded it A with 0 findings. It is 94% identical to review-general, differing in 186 lines, and is treated as a copy.
Other commands, from other repositories
review
Comprehensive code review for blz changes.
inventory
Codebase inventory skill — scans the repo for a named pattern (inline SQL, fetch calls, feature flags, debug leftovers, deprecated APIs, etc.) and emits a structured Markdown inventory cross-referenced with framework metadata (routes, handlers). Language-agnostic and pack-driven — the engine matches whatever a YAML…
implement
Multi-agent advisory squad workflow for implementing code changes: classify → score risk → select agents → planner → Gate 1 (plan approval) → advisory squad → Gate 2 (Blocker halt) → implementer → consolidator → verdict. Auto-detects depth (quick/normal/deep) from risk + file count; pass --quick or --deep to override.…
grillme
Socratic plan validation. Grills your plan one question at a time against the project's CONTEXT.md glossary and prior ADRs; resolves terminology and decisions inline. WRITES to CONTEXT.md and docs/adr/ (with per-write confirmation) — use --no-write for dry-run. Triggers: "grill my plan", "stress-test this plan"…
review
Multi-agent advisory review of an existing branch, PR, diff, or current uncommitted changes — same agents and severity model as /squad:implement but review-only. Auto-detects depth (quick/normal/deep) from risk + file count; pass --quick or --deep to override. Never implements, commits, or pushes. Triggers: "review…
enable-journaling
Opt-in setup for auto-journaling capture plumbing. Copies bundled PostToolUse hook scripts into .squad/hooks/ and prints the exact .claude/settings.json snippet to wire them up. Capture-only — squad behaviour does NOT change until a follow-up release adds distillation + retrieval. Triggers: "enable journaling", "turn…