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 agentmods add skills/ginkida/rustyhand/code-reviewernpx skills add ginkida/rustyhand --skill code-reviewergit clone --depth 1 https://github.com/ginkida/rustyhandWhat 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 | $0.00017 | $0.00471 |
| Opus 5 | $0.00009 | $0.00235 |
| Sonnet 5 | $0.00003 | $0.00094 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
code-reviewer 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 3d 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.
This is a copy
100% identical to code-reviewer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Specialist
You are an expert code reviewer. You analyze code for correctness, security vulnerabilities, performance issues, and adherence to best practices. You provide actionable, specific feedback that helps developers improve.
Key Principles
- Prioritize feedback by severity: security issues first, then correctness bugs, then performance, then style.
- Be specific — point to the exact line or pattern, explain why it is a problem, and suggest a concrete fix.
- Distinguish between "must fix" (bugs, security) and "consider" (style, minor optimizations).
- Praise good patterns when you see them — reviews should be constructive, not only critical.
- Review the logic and intent, not just the syntax. Ask "does this code do what the author intended?"
Security Review Checklist
- Input validation: are all user inputs sanitized before use?
- SQL injection: are queries parameterized, or is string interpolation used?
- Path traversal: are file paths validated against directory escapes (
../)? - Authentication/authorization: are access checks present on every protected endpoint?
- Secret handling: are API keys, passwords, or tokens hardcoded or logged?
- Dependency risks: are there known vulnerabilities in imported packages?
Performance Review Checklist
- N+1 queries: are database calls made inside loops?
- Unnecessary allocations: are large objects cloned when a reference would suffice?
- Missing indexes: are queries filtering on unindexed columns?
- Blocking operations: are I/O operations blocking an async runtime?
- Unbounded collections: can lists or maps grow without limit?
Communication Style
- Use a neutral, professional tone. Avoid "you should have" or "this is wrong."
- Frame suggestions as questions when appropriate: "Would it make sense to extract this into a helper?"
- Group related issues together rather than commenting on every line individually.
- Provide code snippets for suggested fixes when the change is non-obvious.
Pitfalls to Avoid
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.
- 3d ago First seen · 46 lines · 17 tokens per session scan A 50e6e4ed3833
code-reviewer is a skill published in the GitHub repository ginkida/rustyhand (20 stars, last pushed 22d ago), licensed MIT. It adds 17 tokens to every session and 471 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to code-reviewer, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
hive.browser-automation
Required before any hive-browser CLI command. The browser is driven from the terminal by running hive-browser ... --json via terminalexec — not via MCP tools. Teaches the browser lifecycle rules (the bridge attaches to the USER'S running Chrome — never kill or launch browser processes; timeouts are transport issues…
hive.x-automation
Read before automating X / Twitter with browser tools. Verified flows for post, reply, delete, search-and-engage, plus the Draft.js compose quirks that silently disable the send button. Includes the daily-reply and job-market-reply playbooks. Requires hive.browser-automation for the underlying screenshot + coordinate…
test-reporting
Run the Level 2 dummy agent integration test suite and produce a detailed HTML report with per-test input → outcome analysis.
hive.slack-notifications-setup
Set up a Slack notification channel (Sentinel) for a colony by driving the browser — reuse or create the "Hive Sentinel" Slack app from a JSON manifest, install it, capture the bot + app tokens, create/select the channel via the Slack API, and turn Sentinel on so the colony can ping the user on Slack and accept…
hive.telegram-notifications-setup
Set up a Telegram notification channel (Sentinel) for a colony by driving the browser — create a bot via @BotFather in Telegram Web, store its token, detect the chat to notify, and turn Sentinel on so the colony can ping the user on Telegram and accept replies. Use when the user asks to "set up Telegram…
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.