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/einverne/dotfilesWrote 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/einverne/dotfiles/code-reviewer)<a href="https://agentmods.dev/agents/einverne/dotfiles/code-reviewer"><img src="https://agentmods.dev/badge/agents/einverne/dotfiles/code-reviewer/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/einverne/dotfiles/code-reviewer"><img src="https://agentmods.dev/badge/agents/einverne/dotfiles/code-reviewer.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.00030 | $0.01215 |
| Opus 5.5 | $0.00012 | $0.00486 |
| Sonnet 5.5 | $0.00006 | $0.00243 |
| Haiku 4.5 | $0.00003 | $0.00121 |
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 1mo 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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 1mo ago First seen · 164 lines · 30 tokens per session scan A b9acbba0068a
code-reviewer is an agent published in the GitHub repository einverne/dotfiles (121 stars, last pushed 3d ago), licensed GPL-3.0. It adds 30 tokens to every session and 1,215 once invoked, about $0.0001 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-08-30.
Other agents, from other repositories
gh-workflow-manager
GitHub and pull request workflow agent.
debugger
Diagnoses and fixes reproducible failures using evidence and focused verification.
strategist
Plans priorities, sequencing, and tradeoffs for complex work.
nextjs-agent
Next.js development specialist using Next.js DevTools MCP. Always use this agent to query the Next.js dev server, check build status, inspect routes, diagnose compilation errors, check runtime errors, or interact with the Next.js MCP endpoint. Returns focused diagnostics and recommendations.
skeptical-reviewer
An independent review agent for testing claims, assumptions, and conclusions in documents, code, plans, blogs, and other work. It receives an evaluation method and the material to review, without changing that material.
epistemic-explore
Research agent with enforced epistemic rigor. Classifies all findings as Verified, Inferred, or Guess with cited evidence. Use when investigating code, debugging, exploring unfamiliar systems, or when the user asks to research something. Can persist findings as pkm .ref.md artifacts when instructed.