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/pierry/harness-kit/continuegit clone --depth 1 https://github.com/Pierry/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.00010 | $0.00203 |
| Opus 5 | $0.00005 | $0.00102 |
| Sonnet 5 | $0.00002 | $0.00041 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
continue 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
Resume active pipeline.
- Read state:
python3 .claude/scripts/pipeline.py read. Nofeature_idorcurrent, tell user pipeline idle. Suggest/product-manager:runor/sse:run. - Read next command:
python3 .claude/scripts/pipeline.py next. Prints slash command to invoke. - Show current status line:
python3 .claude/scripts/pipeline.py render. - Invoke next-stage command. Use recorded
feature_idso artifacts land under same name. - After stage completes (file written, approval marker applied), post-write/post-edit hooks update state. Run
/pipeline:continueagain to chain next stage, or stop.
If state has pipeline but no feature_id yet (intent recorded, first stage not started), invoke first stage in pipeline.
User wants to abandon run, suggest /pipeline:reset.
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 · 16 lines · 10 tokens per session scan A 915611150401
continue is a command published in the GitHub repository Pierry/harness-kit (3 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 203 once invoked, about $0.0001 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
setup-pm-skills
Onboard a new user — find out what they do, recommend the right bundles & top skills, and set up a project CONTEXT.md so every skill is tailored to them.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.
config
Command "config" from sdebruyn/fabric-dw-mcp-cli, covering configuration & defaults, http retry budget, sql retry budget, mcp workspace allowlist {#mcp-workspace-allowlist} and mcp server log level.
deps-age
Analyze dependency freshness and maintenance activity.