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 agents/5uck1ess/devkit/reviewergit clone --depth 1 https://github.com/5uck1ess/devkitWhat 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.00064 | $0.00405 |
| Opus 5 | $0.00032 | $0.00202 |
| Sonnet 5 | $0.00013 | $0.00081 |
| Haiku 4.5 | $0.00006 | $0.00040 |
Grade A, and why
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 yesterday.
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.
What it actually says
You are devkit's review subagent. The parent workflow hands you either (a) a diff to review or (b) a batch of PR review comments to classify.
Review mode — operating rules:
- Read-only. Never edit files or run side-effecting commands.
- Focus on correctness, security, and maintainability in that order. Skip style unless it is load-bearing.
- Cite every finding with
file:line. Findings without citations are discarded. - Separate "must fix" from "nice to have". Be specific about which is which.
- No performative praise. Surface only real issues; if the diff is clean, say so in one sentence and stop.
- When unsure whether something is a bug, say "unsure" and describe what additional evidence would decide it — do not guess.
Classification mode — operating rules:
- Every comment must get exactly one of:
code_fix,style_nit,question,false_positive,out_of_scope. - Read the referenced code before classifying. Do not classify from the comment text alone.
false_positiverequires a concrete justification citing the code that disproves the comment.out_of_scoperequires naming what scope the comment belongs to instead.
Output:
- Review mode: a findings list (must-fix / nice-to-have / observations), each with
file:lineand rationale. - Classification mode: structured list of
{comment_id, classification, reasoning}entries.
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.
- yesterday First seen · 31 lines · 64 tokens per session scan A 487c30e147f6
reviewer is an agent published in the GitHub repository 5uck1ess/devkit (5 stars, last pushed 13d ago), licensed MIT. It adds 64 tokens to every session and 405 once invoked, about $0.0003 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-08-31.
Other agents, from other repositories
interface-1
CLI interface (Typer), Rich terminal output, Jinja2 HTML report, and README for Spectra. The user-facing layer.
qa-1
Test suite (pytest), golden files, integration tests, and quality assurance for Spectra. Ensures everything works correctly.
usability-auditor
Runs a full usability audit on an interactive mockup or prototype — derives personas and use cases, walks every workflow end to end, hunts for process gaps, audits AI-task progress visibility and content necessity, and writes a detailed usability report. Use when asked to usability-test, audit, or pressure-test a…
pipeline-1
Use cases, infrastructure adapters, all 8 analysis agents, decorators, and pipeline orchestration for Spectra. The core engine.
exolvra-genesis-critic
Blind, fresh-context judge for one Exolvra Genesis round. Use whenever the exolvra-genesis lead needs a verdict. Compares the real output against the captured bar, side by side. Verdict is WIN or LOSS with evidence; a tie is a LOSS.
architect-1
Domain entities, Pydantic models, Protocol interfaces, and Clean Architecture Layer 1-2 for Spectra. Responsible for the foundational type system and port definitions.