Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add maxence2997/mx-harness --skill mx-team-reviewgit clone --depth 1 https://github.com/maxence2997/mx-harnessWrote 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/skills/maxence2997/mx-harness/mx-team-review)<a href="https://agentmods.dev/skills/maxence2997/mx-harness/mx-team-review"><img src="https://agentmods.dev/badge/skills/maxence2997/mx-harness/mx-team-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.00078 | $0.02363 |
| Opus 5 | $0.00039 | $0.01182 |
| Sonnet 5 | $0.00016 | $0.00473 |
| Haiku 4.5 | $0.00008 | $0.00236 |
Grade A, and why
mx-team-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 7d 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 — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Orchestrator
Trigger
/mx-team-review [diff-spec]
/mx-team-review --repo <path>
Orchestrated mode
Step 6 (interactive review of the report) pauses for the user. When invoked from an orchestrator that declares auto-proceed (e.g. mx-flow Phase 5b), skip the pause: save and display the report, then return control — triage happens in the orchestrator's next step. When invoked directly by the user, Step 6 applies as written.
Step 1: Parse Arguments and Determine Mode
Parse the user's argument to determine the review mode:
| Invocation | Mode | Action |
|---|---|---|
/mx-team-review (no args) |
diff | git diff --cached (staged changes) |
/mx-team-review HEAD~3 |
diff | git diff HEAD~3..HEAD |
/mx-team-review main..HEAD |
diff | git diff main..HEAD |
/mx-team-review abc..def |
diff | git diff abc..def |
/mx-team-review --repo src/service/ |
repo | Read all code files in directory |
/mx-team-review --repo src/service/order.go |
repo | Read specific file(s) |
Argument parsing:
- If argument starts with
--repo→ repo mode. The path(s) follow. - Otherwise → diff mode. If no argument, default to
--cached.
Validation:
- Diff mode: run the git diff command. If output is empty, print
No changes to review.and stop. - Repo mode: check if path exists. If not, print error and stop.
Display: 📋 Reviewing: {description of what is being reviewed}
Step 2: Language Detection
Scan file extensions from the diff output (file paths in diff headers) or the target file paths:
| Extension | Language Spec |
|---|---|
.go |
references/golang.md |
.cs |
references/dotnet.md |
| other | skip (no language spec loaded) |
Always load references/principles.md (cross-language core
principles). Then load the matched language-specific spec file(s).
If multiple languages detected, load all matched specs.
Reference files are located relative to this SKILL.md file (sibling
references/ directory).
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 292 lines · 78 tokens per session scan A e566ed6c68fb
mx-team-review is a skill published in the GitHub repository maxence2997/mx-harness (5 stars, last pushed 11d ago), licensed MIT. It adds 78 tokens to every session and 2,363 once invoked, about $0.0004 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 skills, from other repositories
cn-check
Install and run the Continue CLI (cn) to execute AI agent checks on local code changes. Use when asked to "run checks", "lint with AI", "review my changes with cn", or set up Continue CI locally.
resolve-pr-comments
Evaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments. Handles both change requests (fix or skip) and reviewer questions (explain using reasoning recalled from past Claude Code transcripts). Use when the user asks to "resolve PR comments", "fix review comments", "address PR…
review-code
Review code for bugs, security vulnerabilities, API misuse, consistency issues, simplicity problems, or test coverage gaps by running internal reviews and a peer review in parallel and returning combined findings. Single-concern with a type argument, or full review with no argument. Use when the user asks to "review…
assess-technical-debt
Assess project-wide structural technical debt: complexity hotspots, deprecated API usage, duplication clusters, and architecture rot. Ranks findings by impact and refactor effort into a report at .turbo/technical-debt.md. Use when the user asks to "assess technical debt", "find technical debt", "review technical…
map-codebase
Deep architecture report that fans out parallel inspections across different aspects of the codebase (structure, tech stack, APIs, patterns, data flow, dependencies, testing) and synthesizes findings into a comprehensive document at .turbo/codebase-map.md and .turbo/codebase-map.html. Use when the user asks to "map…
peer-review
Run an independent peer review via Codex. Use when the user asks to "peer review", "peer review my code", "peer review my plan", "get a second opinion", or "independent review".