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/assafkip/kipi-system/prd-splitgit clone --depth 1 https://github.com/assafkip/kipi-systemWhat 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.00012 | $0.00318 |
| Opus 5 | $0.00006 | $0.00159 |
| Sonnet 5 | $0.00002 | $0.00064 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
prd-split 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 3d 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-split — 100% identical, 0 lines differ
What it actually says
Materialize the PRD's ## Issues fenced JSON manifest into issue specs under
issues_dir. The split script enforces:
- PRD status is
approved. - Every entry has non-empty
allowed_filesand non-emptyrequired_checks. (An emptyrequired_checkssilently bypasses the runner's verification gate — the split refuses to create such specs.) - No existing issue file is clobbered. Re-runs are idempotent only when byte-identical.
Two-step flow — dry-run first so the author can see planned writes before any file lands on disk:
- Dry-run:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/prd_split.py" --dry-run
Read the would_create paths back to the author. Confirm before committing.
If they do not confirm, stop. Do NOT run step 2 without explicit agreement.
- Commit:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/prd_split.py"
On collision, the script names the divergent files. Do not delete or overwrite them. Ask the author to rename either the manifest entry or the existing file.
After a successful split, tell the author to archive or clear the PRD before
starting an issue (prd_runner.py archive or prd_runner.py clear). The
concurrency guard blocks loading an issue while a PRD context is active.
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.
- 3d ago First seen · 39 lines · 12 tokens per session scan A 000d7021e961
prd-split is a command published in the GitHub repository assafkip/kipi-system (108 stars, last pushed 2d ago), licensed MIT. It adds 12 tokens to every session and 318 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
capture
Search first: /mnemonic:search {relevantkeywords} Capture after: /mnemonic:capture {namespace} "{title}".
integrate
Wire mnemonic memory operations into other Claude Code plugins.
recall
Recall memories with filtering and search.
add-test
Interactively add a new test definition to the test suite.
custodian
Unified memory custodian for audits, validation, and maintenance.
query
Structured frontmatter queries using yq.