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 skills add Tholem-AI/Tholem-Hermes-Kit --skill reviewer-agentgit clone --depth 1 https://github.com/Tholem-AI/Tholem-Hermes-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/skills/tholem-ai/tholem-hermes-kit/reviewer-agent)<a href="https://agentmods.dev/skills/tholem-ai/tholem-hermes-kit/reviewer-agent"><img src="https://agentmods.dev/badge/skills/tholem-ai/tholem-hermes-kit/reviewer-agent/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/skills/tholem-ai/tholem-hermes-kit/reviewer-agent"><img src="https://agentmods.dev/badge/skills/tholem-ai/tholem-hermes-kit/reviewer-agent.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.00023 | $0.01075 |
| Opus 5.5 | $0.00009 | $0.00430 |
| Sonnet 5.5 | $0.00005 | $0.00215 |
| Haiku 4.5 | $0.00002 | $0.00108 |
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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
reviewer-agent
Overview
Verify implementation quality, policy alignment, and release readiness before closure. The reviewer is the final gate — it presents findings ordered by severity and recommends whether work is ready for release.
When to Use
- Use after execution phase produces completed slices with evidence.
- Use before declaring work complete or merging changes.
- Don't use for mid-execution checks — those belong to the executor's validation gates.
Slice Execution Review
When reviewing a specific slice of completed work (dead code removal, refactoring, bug fix), see references/slice-execution-review.md for the full verification workflow: search for removed symbols, check each removal site, verify line count, live-test the application, and cross-check documentation.
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.
Steps
- Receive executor-agent handoff outputs (one or more, if parallel slices were used).
- Verify each slice against the original plan:
- Were all planned changes applied?
- Were all validation gates satisfied?
- Is evidence complete and traceable?
- Check for correctness issues: bugs, type errors, logic flaws, missing edge cases.
- Check for safety issues: exposed secrets, unsafe defaults, privilege escalation paths.
- Check for regression risk: unintended side effects on unaffected modules.
- Verify documentation continuity:
docs/File-Structure-Reference.md,docs/Project-Constraints.md, and project READMEs are aligned. - Present findings ordered by severity with a release-readiness recommendation.
- Produce a handoff output following the schema below.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 100 lines · 23 tokens per session scan A e4d6d43eabc9
reviewer-agent is a skill published in the GitHub repository Tholem-AI/Tholem-Hermes-Kit (2 stars, last pushed 4mo ago), licensed MIT. It adds 23 tokens to every session and 1,075 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-31.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…