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/briefgit 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/brief)<a href="https://agentmods.dev/commands/mrvladd-d/memobank/brief"><img src="https://agentmods.dev/badge/commands/mrvladd-d/memobank/brief.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.00014 | $0.01106 |
| Opus 5 | $0.00007 | $0.00553 |
| Sonnet 5 | $0.00003 | $0.00221 |
| Haiku 4.5 | $0.00001 | $0.00111 |
Grade A, and why
brief 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.
How it starts
The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/brief - Product Brief input contract
Product Brief is the input contract for /constitution when needed and for /write-prd. It is not a PRD, backlog, marketing document, research report, or task plan.
0) Scope
Use /brief when the concept is clear enough to summarize, or after /brainstorm.
Allowed outputs:
.memory-bank/analysis/index.md.memory-bank/analysis/product-brief.md
Do not create:
- feature docs
- task records
- implementation plans
- research reports
- PRFAQ
.memory-bank/analysis/assumptions.md- command aliases
1) Inputs
Read, when present:
- latest relevant
.memory-bank/analysis/brainstorming/BR-*.md - existing
.memory-bank/analysis/product-brief.md - user-provided concept, notes, or PRD-like text
If brainstorming exists, include it in Source artifacts. If no brainstorming exists, a brief may still be created directly from user input.
2) Create or update Product Brief
Create .memory-bank/analysis/product-brief.md with a concise 1-2 page target.
When creating .memory-bank/analysis/index.md, include:
---
description: Analysis artifact index.
status: active
---
Required structure:
---
description: Product Brief input contract for PRD.
status: draft
type: product-brief
---
# Product Brief
## Metadata
- Status: draft
- Decision: proceed|blocked
- Source artifacts:
- .memory-bank/analysis/brainstorming/BR-<NNN>.md
## 1. One-liner
## 2. Target Users
## 3. Problem
## 4. Current Alternatives
## 5. Value Proposition
## 6. Product Concept
## 7. MVP Scope
## 8. Non-goals
## 9. Success Metrics
## 10. Constraints
## 11. Assumptions
## 12. Risks
## 13. Open Questions
## 14. PRD Input Summary
## 15. Decision
proceed|blocked
The Product Brief frontmatter is required. type must be product-brief, and status should match the current brief state, starting as draft.
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 · 140 lines · 14 tokens per session scan A 864a03b6f251
brief 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,106 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
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.