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/prpgit 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.00025 | $0.00867 |
| Opus 5 | $0.00013 | $0.00434 |
| Sonnet 5 | $0.00005 | $0.00173 |
| Haiku 4.5 | $0.00003 | $0.00087 |
Grade A, and why
prp 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
Generate PRP. Follow .claude/agents/product-manager/guides/pipeline.md for retry, approval, publish, and .claude/shared/pipeline-pattern.md for inputs (resolve-mark-proceed) and eval (adversarial).
Print header card before drafting and footer card after gates run. Format: .claude/scripts/stage-card.md.
Source PRD: user passes path, use it. Else pick most recent in .claude/runtime/outputs/pm/prd/. None found, abort. Tell user to run /product-manager:prd first. .claude/runtime/hooks/product-manager/pre-prp-check.sh blocks if PRD lacks approved marker.
Compute feature_id from source PRD filename (basename without .md). Save PRP to .claude/runtime/outputs/pm/prp/{feature_id}.md so it matches.
Before generating, write the phase start marker by running this script. Do NOT inline date/printf (command-substitution + redirect always trips the permission prompt):
.claude/scripts/marker.sh start .claude/runtime/outputs/pm/.markers/{feature_id}.prp-generate.start
Read:
- source PRD
- .claude/runtime/outputs/intake/{feature_id}.md (for resolved repos, squad, metric)
- .claude/agents/product-manager/guides/prp-guidelines.md
- .claude/agents/product-manager/guides/writing-style.md
- .claude/agents/product-manager/guides/templates/prp.md
- .claude/agents/product-manager/guides/pipeline.md
- .claude/agents/product-manager/guides/examples/good-prp-example.md
Explore target repos. Resolve repo paths without asking (resolve-mark-proceed): take them from the intake artifact's repos frontmatter, else context-library/repos.md, else auto-detect from the current working directory and git remotes. Only if none of these yield a path, mark NOT FOUND - NEEDS REVIEW: target repo and proceed. Use Grep and Read to map files. Capture file:line. Never invent paths.
Save to .claude/runtime/outputs/pm/prp/{feature_id}.md.
Sensors: run deterministically via the committed runner. Do NOT improvise inline grep/for loops:
.claude/runtime/scripts/product-manager/run-sensors.sh .claude/runtime/outputs/pm/prp/{feature_id}.md .claude/agents/product-manager/sensors/prp-structure.md .claude/agents/product-manager/sensors/prp-context-quality.md .claude/agents/product-manager/sensors/prp-links.md
Exit 0 = all pass; exit 1 = a sensor blocked (the runner prints which). Read a sensor spec with the Read tool only to explain a failure; never cat it in a loop.
Evals: .claude/agents/product-manager/evals/prp-quality.md, .claude/agents/product-manager/evals/prp-context-readiness.md.
Run the evals adversarially: dispatch a fresh evaluator via the Task tool (subagent_type: general-purpose) that did not author this PRP. Hand it only the artifact path and the two rubric paths; it scores against the rubrics and reports weighted totals plus the low-scoring dimensions. Below threshold (8.0) retries per pipeline.md, regenerating only the flagged dimensions.
After save, reply with this exact shape (name actual sensors/evals/guides that ran):
PRP saved at {path}.
sensors: prp-structure ok, prp-context-quality ok, prp-links ok
eval: prp-quality {N}/10, prp-context-readiness {N}/10
guides: prp-guidelines.md, writing-style.md, templates/prp.md
refs: prd/{feature_id}.md, {target repo paths probed}
next: /sse:plan (ready for handoff)
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 · 54 lines · 25 tokens per session scan A 2ac5d1b7913b
prp is a command published in the GitHub repository Pierry/harness-kit (3 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 867 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
build
Run full verification pipeline.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
camera-ready
Convert an accepted anonymous-submission LaTeX paper (AAAI/AIES/ACM-style) to camera-ready and implement the accepted reviews. Use when a paper is accepted with no rebuttal and you need to de-anonymize, add copyright, turn on section numbering, implement each reviewer's minor revisions, optionally move proofs to a…
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.
generate-rules
Generate development rules and standards into RULES.md.
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.