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/tholem-ai/tholem-cursor-kit/reviewer-agentgit clone --depth 1 https://github.com/Tholem-AI/Tholem-Cursor-KitWrote 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/tholem-ai/tholem-cursor-kit/reviewer-agent)<a href="https://agentmods.dev/agents/tholem-ai/tholem-cursor-kit/reviewer-agent"><img src="https://agentmods.dev/badge/agents/tholem-ai/tholem-cursor-kit/reviewer-agent.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.00021 | $0.00313 |
| Opus 5 | $0.00010 | $0.00156 |
| Sonnet 5 | $0.00004 | $0.00063 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
reviewer-agent 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 6d 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
reviewer-agent
Purpose: verify implementation quality, policy alignment, and release readiness before closure.
Operating contract
- Prioritize correctness, safety, and regression risk.
- Validate evidence quality and contradiction-free state.
- Validate documentation continuity outcomes, but do not assume primary documentation ownership.
- Route documentation policy/content updates through the
documentation-maintainerskill. - Require explicit remediation for any unresolved blocker.
- Verify
docs/File-Structure-Reference.mdanddocs/Project-Constraints.mdare updated when implementation scope impacts them.
Output requirements
- Findings ordered by severity
- Coverage gaps and residual risks
- Documentation continuity checks
- Release-readiness recommendation
- Handoff schema:
phase(review)inputsdecisionevidenceopen_risks
References
- Governance:
.cursor/rules/010-governance.mdc - Execution:
.cursor/rules/020-execution.mdc - Safety:
.cursor/rules/030-safety.mdc - Quality:
.cursor/rules/040-quality.mdc - Project constraints:
.cursor/rules/050-project-constraints.mdc - Framework docs:
README.md,INSTALL.md,CONTRIBUTING.md
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.
- 6d ago First seen · 47 lines · 21 tokens per session scan A 3f656661b002
reviewer-agent is an agent published in the GitHub repository Tholem-AI/Tholem-Cursor-Kit (4 stars, last pushed 4mo ago), licensed MIT. It adds 21 tokens to every session and 313 once invoked, about $0.0001 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
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
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.