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/prd-os/prd-os-initgit clone --depth 1 https://github.com/assafkip/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/prd-os/prd-os-init)<a href="https://agentmods.dev/commands/assafkip/prd-os/prd-os-init"><img src="https://agentmods.dev/badge/commands/assafkip/prd-os/prd-os-init.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 | $0.00015 | $0.00243 |
| Opus 5 | $0.00008 | $0.00121 |
| Sonnet 5 | $0.00003 | $0.00049 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
prd-os-init 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 5d 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.
This is a copy
100% identical to prd-os-init — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
One-time bootstrap. Writes .prd-os/config.json with the default directory
layout so every runner (prd_runner.py, issue_runner.py, prd_split.py,
findings_writer.py) resolves the same paths. The runners refuse to operate
without this file; this command creates it.
Idempotent and non-destructive: if a config already exists it is left untouched.
Pass --force only to overwrite a customized config back to defaults.
Run:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/prd_os_init.py"
Output is JSON:
{"initialized": "<path>"}— config written and validated.{"exists": "<path>", "note": "..."}— already initialized; nothing changed.
Exit codes:
0— initialized, or already initialized.2— repo root could not be resolved (run inside a git repo), or the written config failed to load.
After success, the author can run /prd-start <slug> to create the first PRD.
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.
- 5d ago First seen · 30 lines · 15 tokens per session scan A bb2ad744010b
prd-os-init is a command published in the GitHub repository assafkip/prd-os (10 stars, last pushed 2mo ago), licensed MIT. It adds 15 tokens to every session and 243 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to prd-os-init, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
plan-phase
Wraps superpowers:writing-plans with RENATA guardrails to produce a method-compliant, ADR-respecting execution plan reviewed by the architect.
adopt
Adopts RENATA in an existing codebase — reverse-engineers the technical pattern, feature inventory, as-built specs and a retroactive PRD, confirming every item with you.
screens
Structures product UX screen design — inventory, flow, states, and reusable briefs for external design tools — without generating pixels or UI code.
adr
Formalizes an ADR from a technical decision using the Nygard format and syncs its enforcement block in rules.yaml.
assumption-test
Surfaces the riskiest business assumption behind the PRD and designs the cheapest test to falsify it before building.
hypothesis-check
Confronts each PRD hypothesis with the real measured number, forces an explicit verdict, and triggers a concrete action.