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/reviewer-performance)<a href="https://agentmods.dev/agents/jamie-bitflight/claude_skills/reviewer-performance"><img src="https://agentmods.dev/badge/agents/jamie-bitflight/claude_skills/reviewer-performance/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/agents/jamie-bitflight/claude_skills/reviewer-performance"><img src="https://agentmods.dev/badge/agents/jamie-bitflight/claude_skills/reviewer-performance.svg" alt="Reviewed on agentmods" width="80" 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.00120 | $0.00378 |
| Opus 5.5 | $0.00048 | $0.00151 |
| Sonnet 5.5 | $0.00024 | $0.00076 |
| Haiku 4.5 | $0.00012 | $0.00038 |
Grade A, and why
reviewer-performance 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 15d 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.
What it actually says
Performance Reviewer Agent
Before following any other instruction, first load dh:review-performance-change and follow its process step by step.
DH wrapper contract
The dispatch supplies the changed-file/task scope and any Review Context. Pass both to the
reusable skill; its independent source checks apply to claims in that context. Load
dh:review-verdict-contract for the authoritative verdict schema and applicability rules owned
by the DH multi-perspective workflow.
Translate the skill result into exactly one structured performance verdict block. Write that raw JSON block to the current SAM task's Review Results section using sam_task(... append_section="Review Results"). Do not register it as a document artifact and do not modify reviewed files.
Return the DH subagent STATUS envelope after the task-section write. Missing required task/scope inputs or an unwritable Review Results section is BLOCKED.
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.
- 15d ago Changed · +3 lines 74fd154baeab
- 28d ago Changed · -201 lines 75e476c0e1f0
- 1mo ago Changed · +1 lines 7bfb82640224
- 1mo ago Changed · +3 tokens per session b82eef280a81
- 1mo ago First seen · 226 lines · 117 tokens per session scan A bd631d50031e
reviewer-performance is an agent published in the GitHub repository Jamie-BitFlight/claude_skills (67 stars, last pushed 4d ago), licensed MIT. It adds 120 tokens to every session and 378 once invoked, about $0.0005 per session on Opus 5.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
build-failure-analyst
Expert build-failure analyst for .NET / MSBuild repositories. Invoke when a build produced a binary log (.binlog) and you need to identify the root cause(s) of failure, group related errors, and propose concrete fixes. Queries the binlog live through the binlog-mcp MCP server (containerised — see the calling…
swiftui-performance-analyzer
Use this agent when the user mentions SwiftUI performance, janky scrolling, slow animations, or view update issues — expensive bodies, formatters, whole-collection dependencies, and missing lazy containers.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
predictive-analyst
Precognition agent. Analyzes code changes to predict impact, regressions, and conflicts BEFORE they happen. Uses dependency graphs and historical data.
silent-failure-hunter
Use this agent when reviewing code changes in a pull request to identify silent failures, inadequate error handling, and inappropriate fallback behavior. Invoke it after work involving error handling, catch blocks, fallback logic, or any code that could suppress errors. See "When to invoke" in the agent body for…
silent-failure-hunter
Error handling review agent for CI: identifies silent failures, empty catch blocks, swallowed errors, overly broad exception handling, and missing user feedback in PR diffs.