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/Pierry/harness-kitWrote 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/pierry/harness-kit/pack)<a href="https://agentmods.dev/commands/pierry/harness-kit/pack"><img src="https://agentmods.dev/badge/commands/pierry/harness-kit/pack/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/pierry/harness-kit/pack"><img src="https://agentmods.dev/badge/commands/pierry/harness-kit/pack.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.00018 | $0.00534 |
| Opus 5.5 | $0.00007 | $0.00214 |
| Sonnet 5.5 | $0.00004 | $0.00107 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
pack 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 1mo 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
Build repomix snapshot of target repo. Used by /sse:plan, /sse:sdd supervisor eval, and multi-repo PRPs.
Inputs
- Arg 1 (required):
feature_id(matches PRD/PRP filename basename) - Arg 2 (optional): target repo path (default = cwd)
--include "glob": narrow scope (e.g.--include "src/auth/**"). Repeat with comma-separated globs.--style xml|markdown: output format. Default xml.
Pre-flight
Run command -v repomix. Missing → block with install hint:
repomix not installed
install: npm i -g repomix | brew install repomix
docs: https://repomix.com
Steps
- Bash:
.claude/scripts/pack-repo.sh <feature_id> [target] [--include glob] [--style xml] - Script writes
.claude/runtime/cache/repomix/{feature_id}.{style} - Report path + size + token estimate
When to use
- Target repo > 50 files and stages keep re-grepping same context
- Multi-repo feature: pack each repo, supervisor eval reads concat
- SDD loop: pack
{changed files} ∪ {PRP "Repos and files touched"}for cheaper per-iter eval
When NOT to use:
- Small repo (<20 files): grep is fine
- Pack would exceed context budget (>200k tokens): narrow with
--include
Reply format
Pack complete.
feature: {feature_id}
target: {target_dir}
style: {xml|markdown}
include: {glob | (default .gitignore aware)}
path: .claude/runtime/cache/repomix/{feature_id}.{ext}
size: {N} bytes
tokens: {N} (repomix estimate)
next: consumed automatically by /sse:plan, /sse:sdd if cache present
Cleanup
Pack invalidated when:
/pipeline:resetruns (clears all caches for active feature)- Manual:
rm .claude/runtime/cache/repomix/{feature_id}.*
Pack is snapshot, not live. Re-run when target repo materially changes mid-feature.
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.
- 1mo ago First seen · 60 lines · 18 tokens per session scan A 95b3ea5355a1
pack is a command published in the GitHub repository Pierry/harness-kit (4 stars, last pushed 11d ago), licensed MIT. It adds 18 tokens to every session and 534 once invoked, about $0.0001 per session on Opus 5.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
context-stats
Display context window usage and token statistics.
sync
Session bootstrap - read project context, restore saved state, show status. Quick orientation with optional deep dive.
handoff
Write a session handoff document for continuity.
checkpoint
Write a new link in the continuum chain summarizing decisions/changes since the last link.
dream
Roll up the last N links into a single phase-digest link; originals move to archived/ (never deleted).
hades-show-proposals
Show pending Asphodel memory update proposals.