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/mrvladd-d/memobank/write-prdgit clone --depth 1 https://github.com/mrvladd-d/memobankWhat 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.00014 | $0.01491 |
| Opus 5 | $0.00007 | $0.00745 |
| Sonnet 5 | $0.00003 | $0.00298 |
| Haiku 4.5 | $0.00001 | $0.00149 |
Grade A, and why
write-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 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.
How it starts
The opening of the file, as written. The whole thing — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/write-prd - Brief + Constitution -> PRD
/write-prd is the PRD-level clarification loop. It resolves high-impact ambiguity before /spec-init builds the SDD route map and /prd decomposes the PRD into Memory Bank L1-L3 artifacts.
0) Input sources
Read the current PRD source. Accept any one of these as the source input:
.memory-bank/analysis/product-brief.md- explicit PRD source text or file provided by the user
- existing
prd.mdor.memory-bank/prd.mdwhen present and being normalized/clarified
Read as optional context when present and relevant:
.memory-bank/constitution.md.memory-bank/analysis/brainstorming/BR-*.md.memory-bank/product.md.memory-bank/requirements.md.memory-bank/glossary.md.memory-bank/invariants.md.memory-bank/spec-index.md.memory-bank/contracts/*.memory-bank/states/*.memory-bank/runbooks/*.memory-bank/testing/*- user-provided context in
$ARGUMENTS
If no Product Brief, explicit PRD source text/file, or existing prd.md / .memory-bank/prd.md is available, stop and ask for /brief or explicit PRD source text.
If the Constitution is missing, stop and ask for /constitution or explicit permission to create the PRD without a Constitution gate.
1) Constitution gate
Compare the PRD source and optional context against .memory-bank/constitution.md.
If the PRD requires changing the Constitution, add this section to .memory-bank/prd.md and stop unless the user explicitly confirms the amendment path:
## Constitution Amendment Candidates
### Candidate 1
- Current principle:
- Conflict:
- Proposed amendment:
- Rationale:
Do not weaken, reinterpret, or silently override the Constitution.
2) Draft PRD
Create or update .memory-bank/prd.md with this frontmatter:
---
description: Product Requirements Document.
status: draft
type: prd
clarification_status: pending
constitution_checked: true
---
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 · 201 lines · 14 tokens per session scan A 32288db9e5fc
write-prd is a command published in the GitHub repository mrvladd-d/memobank (55 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 1,491 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.