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 commands/whieet/harness-kit/plangit clone --depth 1 https://github.com/whieet/harness-kitWhat 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 | $0.00060 | $0.00387 |
| Opus 5 | $0.00030 | $0.00193 |
| Sonnet 5 | $0.00012 | $0.00077 |
| Haiku 4.5 | $0.00006 | $0.00039 |
Grade A, and why
plan 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.
What it actually says
/harness-kit:plan
Drive a disciplined plan for the requested change.
Steps
-
Read
.harness/config.jsonfirst and follow itslanguagepreference for AI interaction and generated plan content. Do not translate file/directory names, command names, or config keys. -
Read the project plan template (
<plan.dir>/_template.md, whereplan.dircomes from.harness/config.json) so your plan matches the project's expected structure and Definition-of-Done format. -
Investigate enough to plan well: search for existing utilities/patterns to reuse, identify the files to change, and consider edge cases (empty/error states, performance, regressions).
-
Enter plan mode and present a plan with: Context (why), the approach, the affected files, step-by-step actions with their verification method, and a Definition of Done whose items are checkable.
-
On approval, the
on-plan-approvedhook automatically writes the plan into<plan.dir>/active/. As you implement, check off the DoD items — the Stop-hook gate verifies them before you can finish, andharness-check-plan-dodreminds you to archive the plan tocompleted/when done.
Notes
- For changes ≤ ~20 lines with no interface change, a full plan is optional — but still run
/harness-kit:verifybefore declaring done. - If you edit planned code (
plan.codeGlob) with no covering plan, the plan-gate hook auto-scaffolds one for you to fill in.
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.
- 2d ago First seen · 24 lines · 60 tokens per session scan A 50b486e3748c
plan is a command published in the GitHub repository whieet/harness-kit (5 stars, last pushed 1mo ago), licensed MIT. It adds 60 tokens to every session and 387 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.