Borrowing it
Nothing to install: this file belongs to GSA-TTS/agentic-coding-playbook. 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/GSA-TTS/agentic-coding-playbook/main/.agents/skills/code-review/SKILL.mdgit clone --depth 1 https://github.com/GSA-TTS/agentic-coding-playbookWrote 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/gsa-tts/agentic-coding-playbook/code-review)<a href="https://agentmods.dev/skills/gsa-tts/agentic-coding-playbook/code-review"><img src="https://agentmods.dev/badge/skills/gsa-tts/agentic-coding-playbook/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/gsa-tts/agentic-coding-playbook/code-review"><img src="https://agentmods.dev/badge/skills/gsa-tts/agentic-coding-playbook/code-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00016 | $0.02332 |
| Opus 5.5 | $0.00006 | $0.00933 |
| Sonnet 5.5 | $0.00003 | $0.00466 |
| Haiku 4.5 | $0.00002 | $0.00233 |
Grade A, and why
code-review scanned grade A with 1 finding 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 13d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
| 5.5 | No eval/exec with external data | No `eval()`, `exec()`, `Function()`, `child_process.exec(untrusted)` | How it starts
The opening of the file, as written. The whole thing — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review and PR Workflow
Review AI-assisted code changes and create compliant pull requests.
Context loading: When writing code, load docs/CODING_STANDARDS_COMPACT.md (~500 words). When reviewing code, load the full docs/CODING_PRACTICES.md (~4,100 words). This skill references both.
| Path | Kind | Notes |
|---|---|---|
docs/CODING_STANDARDS_COMPACT.md |
playbook-source | See AGENTS.md §13.1a if not found at this relative path. |
docs/CODING_PRACTICES.md |
playbook-source | Referenced throughout, incl. Steps 1 and 4. See AGENTS.md §13.1a if not found at this relative path. |
When to Use
- Before creating a pull request with AI-assisted changes
- When reviewing code that an AI agent generated or modified
- When a user asks "review this code" or "create a PR"
- After completing a feature or bug fix, before merge
Step 1: Pre-PR Checks
Run automated checks before creating the PR. Fix all failures before proceeding.
1.1 Linter, Formatter, and Tests
Run the project's linter and full test suite. Detect the toolchain from config
files (e.g., npm run lint && npm test, ruff check . && pytest,
go vet ./... && go test ./...). All tests MUST pass before proceeding. If no
linter is configured, flag this as a gap.
1.2 Secrets Scan
Run gitleaks detect --no-git -v (or grep the diff for key/secret/token/password
patterns as a fallback). Any match MUST be investigated and real secrets removed
immediately. See docs/CODING_PRACTICES.md Section 4.
1.3 Size and Complexity
Verify the changes respect project limits (per docs/CODING_PRACTICES.md Section 13.3):
- Functions: 50 lines or fewer
- Files: 400 lines or fewer (400-600 acceptable with justification)
- Cyclomatic complexity: 10 or fewer per function
- Parameters: 5 or fewer per function
Flag violations in the PR description with justification if they are intentional.
1.4 Comment Content
Re-read every comment the change added or touched. Review comments matching one
of these patterns (docs/CODING_PRACTICES.md Section 13.6, full rule at
AGENTS.md Section 15.6.1):
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.
- 13d ago Changed · +27 lines 6e5c36beed9c
- 1mo ago Changed · +5 lines eee031503c6d
- 1mo ago First seen · 190 lines · 16 tokens per session scan A c4b61b803239
code-review is a skill published in the GitHub repository GSA-TTS/agentic-coding-playbook (37 stars, last pushed yesterday), licensed CC0-1.0. It adds 16 tokens to every session and 2,332 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…