Borrowing it
Nothing to install: this file belongs to cafitac/hermit-agent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/cafitac/hermit-agent/main/.claude/commands/code-apply-hermit.mdgit clone --depth 1 https://github.com/cafitac/hermit-agentWrote 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/commands/cafitac/hermit-agent/code-apply-hermit)<a href="https://agentmods.dev/commands/cafitac/hermit-agent/code-apply-hermit"><img src="https://agentmods.dev/badge/commands/cafitac/hermit-agent/code-apply-hermit/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/commands/cafitac/hermit-agent/code-apply-hermit"><img src="https://agentmods.dev/badge/commands/cafitac/hermit-agent/code-apply-hermit.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.00000 | $0.01173 |
| Opus 5.5 | $0.00000 | $0.00469 |
| Sonnet 5.5 | $0.00000 | $0.00235 |
| Haiku 4.5 | $0.00000 | $0.00117 |
Grade A, and why
code-apply-hermit 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/code-apply-hermit — Claude reads the review, Hermit applies it
Hands the P1–P5 findings from the most recent /code-review to Hermit
so Claude doesn't burn tokens re-reading every file and retyping every
edit. Claude stays on judgment; Hermit does the mechanical apply.
Arguments
$ARGUMENTS — PR number, optionally followed by severity filters.
Examples: 123, 123 P1 P2 P3.
--model <model_name>— which executor model Hermit should run. Defaults to the gateway's active model (./bin/gateway.sh --statusto see the current pick).
Prerequisites
- A
/code-reviewoutput from the previous turn in this conversation. - Hermit gateway + MCP server running.
Workflow
Step 1 — locate the worktree
If the argument contains a PR number, follow the repo's worktree convention to resolve the worktree path (or infer from the current branch if you are already inside it). If no worktree / PR info can be resolved, ask the user which directory to operate on.
Step 2 — harvest review findings
Scan the prior conversation for the last /code-review output and
extract each finding: severity, file path, line number, description,
and the proposed direction.
If no review output is present, stop and tell the user to run
/code-review $ARGUMENTS first.
Step 3 — choose what to apply
- Default: every P1 through P5 item.
- Filter: if severities are listed in
$ARGUMENTS(e.g.P1 P2), apply only those.
Step 3.5 — write findings to disk
Save the selected findings to:
.omc/reviews/<branch>-review-<YYYYMMDDHHMMSS>.md
Format:
# Code Review Findings — <branch>
## P1
- `path/to/file.py:42` — short description — suggested fix
## P2
- ...
Step 4 — concurrency lock
mkdir -p .hermit
cat > .hermit/active-task.lock <<EOF
{
"task_id": "<filled-after-run_task>",
"started_at": "$(date -Iseconds)",
"skill": "code-apply-hermit",
"pr": "$ARGUMENTS",
"cwd": "<worktree_path>",
"findings": "<findings_file_path>"
}
EOF
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 · 158 lines · 0 tokens per session scan A ee66af184cab
code-apply-hermit is a command published in the GitHub repository cafitac/hermit-agent (4 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,173 tokens. 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 commands, from other repositories
wayfinder-review
You are a code review specialist. Identify genuine issues while filtering out false positives.
mach12:issue-review
Read a GitHub issue and all comments, review the implementation plan, and present findings.
mach12:pr-review-assessment
Independently assess each finding from a PR review and classify it.
code-review
A structured review of code changes using four checks: risk, resilience, readability, and reliability. It produces a review report for the change.
review
Perform a comprehensive code review on the following target.
simplify
Code simplification review — find duplication, dead code, over-abstraction, and missed reuse.