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 johnfkoo951/cmdspace-plugins --skill code-reviewgit clone --depth 1 https://github.com/johnfkoo951/cmdspace-pluginsWrote 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/johnfkoo951/cmdspace-plugins/code-review)<a href="https://agentmods.dev/skills/johnfkoo951/cmdspace-plugins/code-review"><img src="https://agentmods.dev/badge/skills/johnfkoo951/cmdspace-plugins/code-review/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/skills/johnfkoo951/cmdspace-plugins/code-review"><img src="https://agentmods.dev/badge/skills/johnfkoo951/cmdspace-plugins/code-review.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.00053 | $0.00532 |
| Opus 5.5 | $0.00021 | $0.00213 |
| Sonnet 5.5 | $0.00011 | $0.00106 |
| Haiku 4.5 | $0.00005 | $0.00053 |
Grade A, and why
code-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 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.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review — Deep Quality Analysis
Performs thorough code quality review with structured findings.
Workflow
Step 1: Determine Review Scope
Use AskUserQuestion:
{
"questions": [
{
"question": "What should I review?",
"header": "Scope",
"options": [
{"label": "Recent changes (Recommended)", "description": "Review uncommitted changes or recent commits"},
{"label": "Specific files", "description": "Review specific files or directories you specify"},
{"label": "Full project", "description": "Broad quality assessment of the entire codebase"},
{"label": "PR review", "description": "Review changes in a pull request"}
],
"multiSelect": false
},
{
"question": "What aspects should I focus on?",
"header": "Focus",
"options": [
{"label": "All aspects (Recommended)", "description": "Readability, performance, maintainability, best practices"},
{"label": "Performance", "description": "Focus on performance issues, N+1 queries, memory leaks"},
{"label": "Architecture", "description": "Focus on design patterns, SOLID principles, coupling"},
{"label": "Readability", "description": "Focus on naming, structure, clarity"}
],
"multiSelect": false
}
]
}
Step 2: Gather Code
Based on scope:
- Recent changes: Run
git diffandgit statusto identify changed files - Specific files: Read the specified files
- Full project: Dispatch explorer (Haiku) first, then review key files
- PR review: Use
gh pr diffto get PR changes
Step 3: Review
Dispatch code-reviewer (Sonnet) with the gathered code and focus area.
For "Full project" or "Architecture" focus, also dispatch critic (Opus) for deeper structural analysis.
Step 4: Present Results
Present the code-reviewer's structured report with severity-rated findings.
If both code-reviewer and critic were dispatched, merge their findings into a single report with clear attribution.
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 · 67 lines · 53 tokens per session scan A 8957659108ca
code-review is a skill published in the GitHub repository johnfkoo951/cmdspace-plugins (7 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 532 once invoked, about $0.0002 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-31.
Other skills, from other repositories
pr-reply
Answer reviewers on your own pull requests in other people's repos: find threads where the ball is on your side, tell humans from bots, do exactly what was asked and reply with evidence. Use at the start of any GitHub session or on a new-review alert. Triggers: /pr-reply, /prr, answer the reviewers, who is waiting on…
outbound-gate
Gate for any outbound message before it leaves: pull request or issue comment, DM, invite, post, email. Use before sending to check facts, tone, platform rules, registry status and AI-slop, and to block text that fails.
codex-review
Cross-vendor code review: this agent reviews the other agent's diff and the other agent reviews this one's, so the final check always comes from a different model. Verdicts are APPROVE or REQUESTCHANGES with file:line references. Triggers: "/codex-review", "cross-review this diff", "have the other vendor check this".
red-first-review
Review someone else's pull request by measuring which of its own guards its own test suite actually catches, via a small mutation matrix. Use when reviewing a PR, checking whether a regression test is real, or asked 'is this change actually tested?', 'does this test do anything', 'mutation test this'.
advisor-intake
An intake workflow for recommendations submitted by external advisors through pull requests or issues in a private GitHub repository. Pull requests propose code or document changes; issues record tasks or discussion.
secondop
Get a second opinion from an external LLM at three checkpoints: T1 is the plan valid, T2 which path at a fork, T3 finish plus a QA breaker that tries to break the result. One structured move per exchange (PROPOSE, COUNTER, VERIFY, ACCEPT, BLOCK) with memory across turns, and every exchange mirrored into a…