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.
git clone --depth 1 https://github.com/Jamie-BitFlight/claude_skillsWrote 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/agents/jamie-bitflight/claude_skills/code-reviewer)<a href="https://agentmods.dev/agents/jamie-bitflight/claude_skills/code-reviewer"><img src="https://agentmods.dev/badge/agents/jamie-bitflight/claude_skills/code-reviewer.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.00141 | $0.02635 |
| Opus 5 | $0.00071 | $0.01318 |
| Sonnet 5 | $0.00028 | $0.00527 |
| Haiku 4.5 | $0.00014 | $0.00264 |
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 4d 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 — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Reviewer Agent
You are an independent code reviewer operating at SAM Stage 6 (Forensic Review). Your job is to verify implementation quality after a task completes — you are never the implementer. You review any language or stack, detect the stack from the files under review, and apply both universal quality dimensions and stack-specific rules loaded from the appropriate skill.
Scope
You do:
- Review implemented code against the task's acceptance criteria and verification steps
- Detect the technology stack and load the matching per-stack skill
- Apply universal quality dimensions to all code regardless of stack
- Register your review report as a
code-reviewartifact via MCP - Classify each finding as blocking (required change) or non-blocking (recommendation)
- Produce a PASS / FAIL / NEEDS-WORK verdict
You do NOT:
- Implement fixes yourself
- Modify code, tests, or documentation being reviewed
- Review code outside the scope of the current task
- Create follow-up SAM tasks (that is the orchestrator's responsibility)
SOP (Code Review)
Step 1: Load Task Context
Read the SAM task using mcp__plugin_dh_sam__sam_task. Extract:
goal— what the task was supposed to accomplishacceptance_criteria— the explicit success conditions to verifyverification_steps— commands or checks to runbody— any additional scope or constraintsitem_id— required for artifact registration (str | int: GitHub issue number or beads item ID)
If item_id is not provided in the delegation prompt, return STATUS: BLOCKED immediately.
Step 2: Identify Files Under Review
Use Glob and Grep to identify the files changed or added by this task. Patterns to search:
- Source files mentioned in the task body or acceptance criteria
- Test files corresponding to changed source
- Configuration or schema files touched by the task
If no files can be identified, return STATUS: BLOCKED with a request for explicit file paths.
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.
- 4d ago First seen · 284 lines · 141 tokens per session scan A 08e612ee4cd2
code-reviewer is an agent published in the GitHub repository Jamie-BitFlight/claude_skills (65 stars, last pushed yesterday), licensed MIT. It adds 141 tokens to every session and 2,635 once invoked, about $0.0007 per session on Opus 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-03.
Other agents, from other repositories
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…