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/analysis)<a href="https://agentmods.dev/commands/mrvladd-d/memobank/analysis"><img src="https://agentmods.dev/badge/commands/mrvladd-d/memobank/analysis/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/analysis"><img src="https://agentmods.dev/badge/commands/mrvladd-d/memobank/analysis.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.00026 | $0.01220 |
| Opus 5.5 | $0.00010 | $0.00488 |
| Sonnet 5.5 | $0.00005 | $0.00244 |
| Haiku 4.5 | $0.00003 | $0.00122 |
Grade A, and why
analysis 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/analysis - Analysis router
Analysis is optional. Use it when the product idea is vague, product direction is unstable, or the user asks what should happen before /prd.
0) Scope
/analysis is a router only.
Allowed outputs:
- create
.memory-bank/analysis/index.mdif it does not exist - update
.memory-bank/analysis/index.mdwith current state and the recommended next step - report the next command to the user
Do not create:
.memory-bank/analysis/product-brief.md.memory-bank/analysis/brainstorming/BR-*.md.memory-bank/tasks/*.task.json.memory-bank/tasks/plans/*.memory-bank/analysis/assumptions.md- research reports
- PRFAQ artifacts
- command aliases
1) Inspect state
Check only what is needed:
prd.md.memory-bank/constitution.md.memory-bank/analysis/index.md.memory-bank/analysis/product-brief.md.memory-bank/analysis/brainstorming/BR-*.md.memory-bank/features/FT-*.md- clear brownfield signals such as source code,
package.json,go.mod,Cargo.toml,requirements.txt, or existing app folders
Do not infer a roadmap from a brownfield codebase before mapping it.
2) Ensure index when useful
If .memory-bank/analysis/index.md is missing and Analysis is the selected path, create it with:
- YAML frontmatter:
description: Analysis artifact index.status: active
- current state
- artifact links
- recommended next step
- open routing questions
Use this frontmatter:
---
description: Analysis artifact index.
status: active
---
Do not create .memory-bank/analysis/ in a clean skeleton unless /analysis, /brainstorm, or /brief is actually being used.
3) Routing table
When routing from an existing Product Brief or PRD/delta source toward /write-prd, first inspect .memory-bank/constitution.md project_principles.
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 · 118 lines · 26 tokens per session scan A 0dcebefc97b9
analysis is a command published in the GitHub repository mrvladd-d/memobank (56 stars, last pushed 4mo ago), licensed MIT. It adds 26 tokens to every session and 1,220 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
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.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.
speckit.bug.test
Validate that a previously fixed bug is resolved and record the verification report.