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.
git clone --depth 1 https://github.com/mrvladd-d/memobankWrote 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/mrvladd-d/memobank/prd)<a href="https://agentmods.dev/commands/mrvladd-d/memobank/prd"><img src="https://agentmods.dev/badge/commands/mrvladd-d/memobank/prd/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/mrvladd-d/memobank/prd"><img src="https://agentmods.dev/badge/commands/mrvladd-d/memobank/prd.svg" alt="Reviewed on agentmods" width="80" 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.00019 | $0.01462 |
| Opus 5.5 | $0.00008 | $0.00585 |
| Sonnet 5.5 | $0.00004 | $0.00292 |
| Haiku 4.5 | $0.00002 | $0.00146 |
Grade A, and why
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 1mo 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/prd - Clarified PRD -> Memory Bank
/prd does not write the PRD, ask Deep Questioning questions, create TASK records, create implementation plans, or require feature-level clarification.
/prd requires .memory-bank/spec-index.md as the lightweight SDD route map and reads only relevant existing authoritative specs routed by that index before deriving L1-L3.
0) Required PRD input
Require .memory-bank/prd.md and .memory-bank/spec-index.md.
Its frontmatter must include:
type: prd
clarification_status: complete
constitution_checked: true
If .memory-bank/prd.md is missing, stop and tell the user to run /write-prd.
If clarification_status is pending or blocked, stop and continue /write-prd.
If constitution_checked is not true, stop and run /write-prd or resolve the Constitution gate.
If the PRD contains unresolved NEEDS CLARIFICATION blockers in decomposition-relevant sections, stop and run /write-prd.
Read .memory-bank/constitution.md before writing derived docs. If the PRD conflicts with the Constitution, stop and ask for explicit resolution or /constitution amendment.
SDD route map gate
.memory-bank/spec-index.md is a required lightweight SDD route map for /prd after /spec-init.
Before writing derived docs:
- read
.memory-bank/spec-index.mdas a route map, not as a substitute for the specs; - stop and run
/spec-initif.memory-bank/spec-index.mdis missing, stale, placeholder-only, ambiguous, has broken links, or cannot safely identify relevant existing specs and planned/candidate/unknown/not_applicable areas; - determine relevance from PRD sections, affected product areas, requirements, actors, data/domain model, contracts/APIs, states/lifecycles, security/compliance, runtime/operations, and verification strategy;
- resolve and read only the relevant authoritative spec files routed by
.memory-bank/spec-index.md; - do not load every SDD spec by default; leave non-relevant authoritative specs closed unless the index routes them into the current PRD/decomposition scope;
- if a relevant authoritative spec conflicts with the PRD, stop and ask for explicit resolution through a spec or PRD amendment instead of silently overriding either source.
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.
- 1mo ago First seen · 126 lines · 19 tokens per session scan A bc1aa1596759
prd is a command published in the GitHub repository mrvladd-d/memobank (56 stars, last pushed 4mo ago), licensed MIT. It adds 19 tokens to every session and 1,462 once invoked, about $0.0001 per session on Opus 5.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
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
sync-linear
Sync current work with Linear ticket status.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.