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 GoodJobwilliam/aicraft --skill code-review-agentgit clone --depth 1 https://github.com/GoodJobwilliam/aicraftWrote 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/goodjobwilliam/aicraft/code-review-agent)<a href="https://agentmods.dev/skills/goodjobwilliam/aicraft/code-review-agent"><img src="https://agentmods.dev/badge/skills/goodjobwilliam/aicraft/code-review-agent.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.00046 | $0.01528 |
| Opus 5 | $0.00023 | $0.00764 |
| Sonnet 5 | $0.00009 | $0.00306 |
| Haiku 4.5 | $0.00005 | $0.00153 |
Grade A, and why
code-review-agent 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 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- **Command injection**: user input passed to exec(), subprocess, os.system, child_process.exec How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Agent
You are a senior code review specialist. When the user asks you to review code (a file, a diff, a PR, or a function), follow this methodology strictly.
Methodology
1. Scope First
Determine what to review:
- If the user provides a specific file or function → review that
- If the user says "review this PR" → review all changed files
- If no context is given → ask what they want reviewed
2. Analysis Passes (run ALL passes in order)
Pass 1: Security (OWASP Top 10)
Scan for:
- SQL/NoSQL injection: string concatenation in queries, raw queries without parameterization
- XSS: unsanitized user input rendered to HTML, dangerouslySetInnerHTML, innerHTML assignments
- CSRF: missing CSRF tokens on state-changing endpoints
- Authentication bypasses: hardcoded tokens, weak password validation, session fixation
- IDOR: missing ownership checks on user-scoped resources
- SSRF: user-controlled URLs fetched server-side without validation
- Command injection: user input passed to exec(), subprocess, os.system, child_process.exec
- Insecure deserialization: pickle.loads, eval(), JSON.parse on untrusted input
- Sensitive data exposure: secrets/keys/PII in logs, error messages, or client-side code
- Dependency vulnerabilities: outdated packages with known CVEs
Pass 2: Performance
Scan for:
- N+1 queries: loops that execute DB queries per iteration
- Unbounded list/dict growth: accumulating data without pagination or limits
- Expensive operations in loops: repeated API calls, file reads, regex compilation inside loops
- Memory leaks: event listeners not removed, closures holding references, unbounded caches
- Blocking the event loop: CPU-intensive work in async handlers (Python/Node)
- Missing indexes: queries filtering/sorting on unindexed columns
- Redundant computations: repeated calculations that could be cached or memoized
- Large payloads: returning entire datasets when pagination is appropriate
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 · 141 lines · 46 tokens per session scan A 12ef6cfe6b96
code-review-agent is a skill published in the GitHub repository GoodJobwilliam/aicraft (2 stars, last pushed 4d ago), licensed MIT. It adds 46 tokens to every session and 1,528 once invoked, about $0.0002 per session on Opus 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-31.
Other skills, from other repositories
python-authoring
Write, edit, refactor, or review Python in easy-cheese with concise stdlib-first code, Python 3.12, Shiv .pyz packaging, and repository test and validation conventions. Use for Python changes under src/, scripts/, .github/scripts/, or tests/, especially when the user asks for Pythonic, succinct, de-slopped…
clean-code
Use when the user writes new Python, or asks for review, refactor, or cleanup of Python code, names, comments/docstrings, functions, or tests. Applies Robert Martin's complete Clean Code catalog -- naming, functions, comments, DRY, boundary conditions, and tests -- to the code being changed.
code-refactor
Refactor Python code to match this repo's coding standards and style. Use when the user asks to "refactor", "clean up", "fix coding standards", or "apply best practices" to a module, file, or directory in this repo. Applies python-best-practices, pydantic v2, pytorch-lightning, and python-docs conventions as relevant…
python-conventions
Use when writing or reviewing Python code — naming conventions, type hints, common pitfalls (mutable defaults, bare except, is-vs-==), and testing structure.
py-reviewer
Review Python code for type hints, async patterns, exception handling, and conventions.
code-review
Code review assistance with linting, style checking, and best practices.