Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add assafkip/kipi-system/plugin install prd-osWrote 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/assafkip/kipi-system/prd-start)<a href="https://agentmods.dev/commands/assafkip/kipi-system/prd-start"><img src="https://agentmods.dev/badge/commands/assafkip/kipi-system/prd-start.svg" alt="Measured on agentmods" 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.00017 | $0.00340 |
| Opus 5 | $0.00009 | $0.00170 |
| Sonnet 5 | $0.00003 | $0.00068 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
prd-start 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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- prd-start — 88% identical, 2 lines differ
What it actually says
Create a new PRD from the template. The slug becomes part of the PRD id
(prd-<slug>-YYYY-MM-DD). Slug must be kebab-case.
The runner enforces two invariants:
- No other PRD is active and non-archived.
- No issue is active (cross-runner concurrency guard).
Run:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/prd_runner.py" new "$1" --owner "${2:-${USER:-unknown}}"
If the command exits non-zero, surface stderr verbatim. Do not retry. Common rejections:
- slug format (not kebab-case)
- active PRD (advise
/prd-archiveor clear) - active issue (advise closing the issue first)
After success, read the new PRD spec file to the author and ask them to fill in:
- Problem (concrete, observed, measurable)
- Goals and non-goals
- Proposed approach
- Risks and rollback
- Open questions
The template already includes a ## Issues section with an empty [] JSON block. Author content into the existing sections; do not add a second ## Issues heading. The runner blocks advance when the body has more than one ## Issues heading.
Do not auto-draft PRD content. The PRD is the author's contract. Auto-drafting creates sycophantic PRDs that pass review because Claude agreed with itself.
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.
- 6d ago First seen · 35 lines · 17 tokens per session scan A 11b644365dcf
prd-start is a command published in the GitHub repository assafkip/kipi-system (109 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 340 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-30.
Other commands, from other repositories
recall
Recall memories with filtering and search.
add-test
Interactively add a new test definition to the test suite.
run-tests
Run automated functional tests using the hook-driven test framework. Execute the test suite to validate all project functionality.
gc
Garbage collect expired memories.
setup
Configure mnemonic for proactive memory operations.
status
Show mnemonic system status and statistics.