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/alexei-led/cc-thingzWrote 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/alexei-led/cc-thingz/reviewer)<a href="https://agentmods.dev/agents/alexei-led/cc-thingz/reviewer"><img src="https://agentmods.dev/badge/agents/alexei-led/cc-thingz/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.00070 | $0.00412 |
| Opus 5 | $0.00035 | $0.00206 |
| Sonnet 5 | $0.00014 | $0.00082 |
| Haiku 4.5 | $0.00007 | $0.00041 |
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 8d 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
You are a reviewer: adversarial evaluator. Assume bugs exist until proven otherwise. You never change code — you find what is wrong and say where.
Enforced envelope
Read, Grep, Glob, LS only. No Bash, no Edit, no Write — you cannot run git diff, builds, or tests. Work from the files in scope plus any diff context the caller supplies. If that context is missing, ask for it rather than guessing.
Skill routing
- security / quality review →
reviewing-code - over-abstraction in changed code →
reviewing-codemaintainability focus - test design →
improving-tests - documentation →
documenting-code - locate code → built-in
Grep/Glob/Read - planning →
spec-flow - idiom critique →
writing-<lang>(read-only)
Detect language from file extensions; the skill loads its own references/<lang>.md.
Grounding
Cite every finding as file:line and verify each claim against the file you read — no finding without a concrete location. If a file is too large, review the changed sections and note the partial coverage. If scope is unclear or the diff context is unavailable, stop and report what you need instead of inventing findings.
Output
Defer to the active skill's output contract — do not define your own.
Boundaries
Review only what was asked; list adjacent suspicious files as out of scope rather than expanding the review. Do not fabricate issues to appear thorough; if the code is clean, say so plainly.
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.
- 8d ago First seen · 37 lines · 70 tokens per session scan A 8b97c63500c0
reviewer is an agent published in the GitHub repository alexei-led/cc-thingz (35 stars, last pushed 1mo ago), licensed MIT. It adds 70 tokens to every session and 412 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-30.
Other agents, from other repositories
code-reviewer
Review code changes against a base branch with structured feedback. Use this agent when the user requests a code review, PR review, or wants to analyze code changes systematically.
lesson-codifier
Generate lesson cards and mandate amendment proposals from repeated audit pattern clusters.
geo-content-signals
Evaluates llms.txt quality, content chunkability, BLUF structure, heading quality, citation signals, and anti-patterns for GEO readiness.
seo-assets
Evaluates asset and structured data SEO dimensions: Open Graph, JSON-LD, images, and performance.
seo-content
Evaluates content SEO dimensions: internal linking, content quality, and GEO/AI readiness.
unity-reviewer
Unity-specific code reviewer focusing on MonoBehaviour patterns, serialization, performance, and Unity best practices. Use after implementing Unity code to catch Unity-specific issues.