Borrowing it
Nothing to install: this file belongs to cboone/agent-harness-plugins. 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/cboone/agent-harness-plugins/main/.github/skills/code-review/SKILL.mdgit clone --depth 1 https://github.com/cboone/agent-harness-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/cboone/agent-harness-plugins/code-review)<a href="https://agentmods.dev/skills/cboone/agent-harness-plugins/code-review"><img src="https://agentmods.dev/badge/skills/cboone/agent-harness-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/cboone/agent-harness-plugins/code-review"><img src="https://agentmods.dev/badge/skills/cboone/agent-harness-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.00038 | $0.00673 |
| Opus 5.5 | $0.00015 | $0.00269 |
| Sonnet 5.5 | $0.00008 | $0.00135 |
| Haiku 4.5 | $0.00004 | $0.00067 |
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 25d 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 — 30 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review
Apply the checklist that matches each changed file, and apply it only to the lines the pull request changes.
Checklists
- Bash scripts (
bin/*,plugins/*/scripts/*,plugins/*/skills/*/references/scripts/*,tests/fixtures/*, exceptbin/AGENTS.md,bin/CLAUDE.md,**/*.yml):write-bash-scripts.md. Full guide: write-bash-scripts style guide. - Scrut test files (
tests/scrut/**/*.md):write-scrut-tests.md. Full guide: write-scrut-tests style guide. - Markdown files (
**/*.md, excepttests/scrut/**/*.md):write-markdown.md. Full guide: write-markdown style guide.
Reporting
- Start each finding with the checklist name and the rule name, for example
write-bash-scripts: Strict mode. - Rules under a checklist's Important heading block merging. Report each one you find.
- Rules under a checklist's Nits heading are minor. Report at most five per review, and give the number of any others in the summary.
- Follow each checklist's Do not flag section.
- Do not report what these CI checks already report:
markdownlint-cli2,prettier,shellcheck,shfmt,actionlint,bin/validate-json,bin/validate-plugins, themake buildgenerated-mirror drift check,scrut. - Do not review these paths:
yarn.lock,dist/,.agents/,plugins/set-up-review-config/skills/set-up-review-config/references/checklists/,docs/plans/done/,.github/skills/code-review/*.mdexceptSKILL.md. - A script without a file extension follows its shebang: Bash scripts use
write-bash-scripts.md. - Rules outside this block, in this file,
.github/copilot-instructions.md,AGENTS.mdorREVIEW.md, take precedence over it.
What ships with it
3 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.
- 25d ago First seen · 30 lines · 38 tokens per session scan A 14f20d5875e6
code-review is a skill published in the GitHub repository cboone/agent-harness-plugins (2 stars, last pushed 2d ago), licensed MIT. It adds 38 tokens to every session and 673 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-09-21.
Other skills, from other repositories
review-pr
Review a pull request for conceptual fit, architecture impact, adversarial failure modes, security risk, docs impact, regression risk, test coverage, and merge readiness. Use when asked to review a PR, check whether a PR is safe to merge, decide if more tests are needed, perform adversarial or security review, or…
software-code-refactoring
Improve production code quality while preserving all existing test behavior. Commonly used for the Refactor phase of TDD red-green-refactor, but applicable to any codebase with tests. Use when production code works but needs cleanup — reducing duplication, improving naming, simplifying complexity, aligning with…
drift-check
Pre-PR advisory check for deviations from the project spec. Read-only analysis.
review-preflight
Review tooling for a PR: review-preflight prints REVIEW.md's criteria and the PR's live gate state before a review; ci-triage maps a PR's failing checks to already-filed issues.
remarc
Manage Remarc session comments and contextual feedback. Use when the user mentions Remarc sessions, comments, handoff, triage, review, addressing, resolving, status updates, or summaries.
fuck-over-engineering
Use when the user asks what could be deleted or reduced to simplify a codebase, says "simplify", "over-engineered", or wants a repo-, folder-, or file-wide audit for over-engineering — hunts dead code, reinvented stdlib, needless dependencies, and single-implementation abstractions, reports ranked cuts, applies only…