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 skills add mrvladd-d/memobank --skill cold-startgit 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/skills/mrvladd-d/memobank/cold-start)<a href="https://agentmods.dev/skills/mrvladd-d/memobank/cold-start"><img src="https://agentmods.dev/badge/skills/mrvladd-d/memobank/cold-start/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/skills/mrvladd-d/memobank/cold-start"><img src="https://agentmods.dev/badge/skills/mrvladd-d/memobank/cold-start.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.00025 | $0.05266 |
| Opus 5.5 | $0.00010 | $0.02106 |
| Sonnet 5.5 | $0.00005 | $0.01053 |
| Haiku 4.5 | $0.00003 | $0.00527 |
Grade A, and why
cold-start 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 — 420 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cold Start: Memory Bank + Agents bootstrap (greenfield & brownfield)
Summary
Note:
cold-startis the package skill for all-in-one bootstrap. Do not confuse it with the generated project command/cold-start: that command is a lightweight router used after skeleton creation inside a target repo. For modular usage, prefer individual skills:mb-init(skeleton),mb-analysis(optional idea discovery),mb-from-prd(greenfield),mb-map-codebase(brownfield),mb-review(review),mb-execute(implementation),mb-verify(UAT),mb-red-verify(semantic adversarial verification).
- What it does: creates the Memory Bank skeleton, writes agent entry points, and routes the repo into the right workflow.
- Use it when: you want one entry point for either a new project with a PRD or an existing codebase that needs mapping first.
- Input: repository root plus either
prd.md/ requirements text or an existing codebase. - Output:
.memory-bank/,.tasks/,.protocols/, agent entry files, and the next step for greenfield or brownfield work.
Supported scenarios:
- Idea-only: repo has a raw idea, but no stable PRD yet; optionally route through
/analysis,/brainstorm, and/brief. - Clear concept: repo has enough direction for a product brief; normally run
/brief, then/constitutiononly if project principles are not alreadyratified|partial, before/write-prd. - Greenfield: repo has
prd.mdor requirements text, but no code yet. - Brownfield: repo already contains code and needs as-is documentation before change planning.
Non-negotiable principles
1) Orchestrator vs workers
- You (main agent) are the orchestrator. You plan and coordinate.
- Workers (subagents) do the heavy lifting (scanning many files, producing long reports).
- Max depth = 2: orchestrator → subagent. No sub-sub-agents.
2) .tasks/ is runtime memory (НЕ Memory Bank)
- Every agent process gets a unique task folder:
.tasks/TASK-XXX/. - Subagents write detailed outputs there, and return only short summaries to the orchestrator.
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 · 420 lines · 25 tokens per session scan A f5bed775ee9b
cold-start is a skill published in the GitHub repository mrvladd-d/memobank (56 stars, last pushed 4mo ago), licensed MIT. It adds 25 tokens to every session and 5,266 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 skills, from other repositories
knowledge-ingest
Ingest documents, articles, conversations, or supplied text into Knowledge with retained originals, sourced claims, entity updates, timelines, and cross-links; also learn durable lessons from a set of conversations, transcripts, or past sessions (/learn), including the Learn from conversations and Learn from Memory…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
Cortex
LifeOS memory, prior-session recall, and learning capture. USE WHEN capture this learning, document this learning, what did we learn recently, recent learnings, cortex, knowledge, knowledge base, search knowledge, what do we know about, archive, harvest, knowledge status, develop note, add to knowledge, add a people…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…