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-archivegit 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-archive)<a href="https://agentmods.dev/commands/assafkip/prd-os/prd-archive"><img src="https://agentmods.dev/badge/commands/assafkip/prd-os/prd-archive.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.00009 | $0.00279 |
| Opus 5 | $0.00005 | $0.00139 |
| Sonnet 5 | $0.00002 | $0.00056 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
prd-archive 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.
What it actually says
Move the active PRD to archived, the terminal state. Archiving stamps
status: archived and a fresh updated_at onto the spec, then clears the
active-PRD state so a new PRD can start. Any PRD status can be archived
(idea, draft, in-review, approved).
This transition is intentionally not gated: archiving is how you retire a PRD, including one you decided not to pursue. The permanent record is the spec on disk plus its findings JSONL; archiving does not delete either.
Steps:
- Confirm a PRD is active:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/prd_runner.py" status
If no PRD is active, tell the author and stop.
- Archive it:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/prd_runner.py" archive
Output is JSON:
{"archived": "<prd-id>"}— archived and active state cleared.{"archived": "<prd-id>", "note": "already"}— was already archived.
Exit codes:
0— archived (or already archived).2— no active 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 · 38 lines · 9 tokens per session scan A e8cb105c1de6
prd-archive is a command published in the GitHub repository assafkip/prd-os (10 stars, last pushed 2mo ago), licensed MIT. It adds 9 tokens to every session and 279 once invoked, about $0.0000 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
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.
plan-phase
Wraps superpowers:writing-plans with RENATA guardrails to produce a method-compliant, ADR-respecting execution plan reviewed by the architect.
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.