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/kimsanguine/hplanWrote 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/kimsanguine/hplan/harness-handoff)<a href="https://agentmods.dev/commands/kimsanguine/hplan/harness-handoff"><img src="https://agentmods.dev/badge/commands/kimsanguine/hplan/harness-handoff/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/kimsanguine/hplan/harness-handoff"><img src="https://agentmods.dev/badge/commands/kimsanguine/hplan/harness-handoff.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.00062 | $0.00410 |
| Opus 5 | $0.00031 | $0.00205 |
| Sonnet 5 | $0.00012 | $0.00082 |
| Haiku 4.5 | $0.00006 | $0.00041 |
Grade A, and why
harness-handoff 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
/harness-handoff
Instructions
You run the hplan multi-target handoff for: $ARGUMENTS
Step 1 — Verify Build Gate
Confirm harness/decisions.jsonl has a recent decision: "build" (or CONDITIONAL_GO) for this project AND harness/build-gate/checkpoint.json has status: "approved".
Step 2 — Locate the brief JSON
The brief must include at minimum: product_name, problem, icp, jtbd, cogs_ceiling, decision. Other fields fill gaps in generated artifacts.
Step 3 — Execute
python3 hplan/scripts/export_handoff.py <brief.json> --target <spec-kit|kiro|gstack|claude|all> --root .
Step 4 — Place outputs
Help the user move generated files from harness/exports/<target>/ to their actual project location (spec-kit specs/ at repo root, kiro .kiro/ at repo root, gstack /office-hours direct paste, claude AGENTS.md+CLAUDE.md at repo root).
Output Format
Return:
- Targets exported — list of files written per ecosystem
- NNN prefix used — for spec-kit auto-increment
- Next manual step — where to copy the generated files to make the downstream agent see them
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 · 33 lines · 62 tokens per session scan A 64c2fbe0f888
harness-handoff is a command published in the GitHub repository kimsanguine/hplan (2 stars, last pushed 23d ago), licensed MIT. It adds 62 tokens to every session and 410 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-31.
Other commands, from other repositories
openehr-explain
One-stop router that explains or looks up any openEHR thing — auto-detects an archetype, a template, an RM/AM/BASE type, an RM structural concept, an ADL idiom, an AQL query or keyword, or a terminology code (replaces /archetype-explain, /template-explain, /type-spec, /rm-structure, /adl-idiom, /terminology).
start-design-plan
Start collaborative design process with brainstorming and planning.
start-implementation-plan
Create implementation plan from design document.
co-change
List files that historically co-change with a target (git log heuristic; COCHANGE-style).
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.