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/prd)<a href="https://agentmods.dev/commands/kimsanguine/hplan/prd"><img src="https://agentmods.dev/badge/commands/kimsanguine/hplan/prd/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/prd"><img src="https://agentmods.dev/badge/commands/kimsanguine/hplan/prd.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.00059 | $0.00593 |
| Opus 5.5 | $0.00024 | $0.00237 |
| Sonnet 5.5 | $0.00012 | $0.00119 |
| Haiku 4.5 | $0.00006 | $0.00059 |
Grade A, and why
prd 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
/prd — Unified 15-section PRD Writer
Running for: $ARGUMENTS
이 커맨드는 deliver/skills/prd/SKILL.md 스킬을 즉시 호출합니다.
Instructions
deliver/prd스킬을$ARGUMENTS로 invoke.- 스킬이 Phase 1~5(Section 1-15)를 순차 작성.
- 결과 산출물:
docs/PRD.md— 15-section PRDharness/QA_POOL.json— §15 QA Pool (dev_roles 결정론 매핑)
모드 (sub-mode)
- 기본: 15-section PRD 작성.
--mode design-shotgun: 기존 PRD의 §1+§11을 읽어harness/design-variants/에 HTML 변형 4개 + comparison.md 생성.--mode roadmap [generate|rice|prioritize]: §6 Now/Next/Later 기반 로드맵. prd가 §6 canonical 소유자이며 roadmap은 그 sub-mode 다. generate=Mermaid gantt(docs/ROADMAP.md), rice=RICE 결정론 계산(docs/rice-scores.md), prioritize=Now/Next/Later 재분류 제안.
입력 가이드
$ARGUMENTS가 없으면 스킬이 product name을 묻습니다.interview-synthesis audit결과로harness/PERSONA_SPECS.json이 있으면 §15 QA Pool 작성에 자동 활용됩니다.
후속
harness/QA_POOL.json생성 후qa-checklist --mode adversarial실행 가능.- §15 QA Pool 생성을 다음 단계로 미루고 PRD 본문(Section 1-14)만 빨리 작성하려면
harness-build --step prd단축 경로 사용. (단,qa-checklist --mode adversarial은 §15가 있어야 진입 가능 — 사후/prd재호출 필요)
Output Format
기본 모드는 docs/PRD.md와 필요한 경우 harness/QA_POOL.json을 생성합니다. sub-mode는 해당 roadmap 또는 design-variant artifact와 다음 실행 경로를 반환합니다.
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 · 40 lines · 59 tokens per session scan A 24b39b9a7d0f
prd is a command published in the GitHub repository kimsanguine/hplan (3 stars, last pushed 2mo ago), licensed MIT. It adds 59 tokens to every session and 593 once invoked, about $0.0002 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
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).
how-to-customize
Explains how to customize design and implementation plans with project-specific guidance.
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.