feature-develop-hermit

A feature-development command that lets Claude plan and verify a change while Hermit, another AI executor, writes the implementation through MCP, a tool-connection standard.

In plain words
What is it for?
Use it to develop a GitHub pull request or similarly identified task with a plan, code implementation, and final verification. It supports different delegation depths and executor models.
Why use it?
It keeps the detailed implementation output out of Claude’s working context, leaving Claude to coordinate the work and check the result.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/cafitac/hermit-agent/feature-develop-hermit
Clone the repo
git clone --depth 1 https://github.com/cafitac/hermit-agent

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,354 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.02354
Opus 5 $0.00000 $0.01177
Sonnet 5 $0.00000 $0.00471
Haiku 4.5 $0.00000 $0.00235

Measured 2d ago against content hash e8d449c28918, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

feature-develop-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 2d 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.

.claude/commands/feature-develop-hermit.md · 260 lines

How it starts

The opening of the file, as written. The whole thing — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/feature-develop-hermit — Claude plans, Hermit implements

Same outline as /feature-develop, but the Phase 3 implementation is delegated to Hermit over MCP so Claude's context never absorbs the grunt-work tool output.

Claude is the orchestrator (interview, pattern search, plan, final verification). Hermit is the executor (TDD red-green implementation).

Arguments

$ARGUMENTS — PR number (or a short slug if you are not using GitHub PRs).

  • --strategy {aggressive|moderate|conservative} — delegation depth. If omitted, inferred from the model-strategy map in the checkpoint config (see "Checkpoint policy").
  • --model <model_name> — which executor model Hermit should run with (e.g. --model glm-5.1, --model qwen3-coder:30b). If omitted, the gateway's default model is used.

Checkpoint policy

The delegation depth is read from:

$HERMIT_CHECKPOINT_CONFIG  (env override)
  ├── ~/.claude/state/hermit-checkpoints.json  (user-local)
  └── scripts/harness/hermit-checkpoints.default.json  (repo default)

Three strategies

Strategy Claude does Hermit does
aggressive interview · plan review · final verify pattern search · plan doc · implementation
moderate interview · pattern search · plan review · final verify plan doc · implementation
conservative interview · pattern search · plan doc · plan review · final verify implementation only

Auto-selection

If --strategy is absent, query the gateway's active model (./bin/gateway.sh --status or GET /health → active_models[0]) and look it up in the config's model_strategy_map:

  • Prefix or substring match (e.g. glm-5.1glmaggressive)
  • If nothing matches, fall back to default_strategy.

Prerequisites

  • gh CLI authenticated (or skip the GitHub steps if you don't use it)
  • Hermit gateway + MCP server running (./bin/gateway.sh --status)
  • Current branch is the PR branch, or the worktree already exists

Workflow

Read the full file on GitHub · 260 lines

Changes

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.

  1. 2d ago First seen · 260 lines · 0 tokens per session scan A e8d449c28918

Subscribe to this mod's changes

feature-develop-hermit is a command published in the GitHub repository cafitac/hermit-agent (4 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,354 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.