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/DyanGalih/spec-kit-memory-hubWrote 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/dyangalih/spec-kit-memory-hub/speckit.memory-md.prepare-context)<a href="https://agentmods.dev/commands/dyangalih/spec-kit-memory-hub/speckit.memory-md.prepare-context"><img src="https://agentmods.dev/badge/commands/dyangalih/spec-kit-memory-hub/speckit.memory-md.prepare-context/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/dyangalih/spec-kit-memory-hub/speckit.memory-md.prepare-context"><img src="https://agentmods.dev/badge/commands/dyangalih/spec-kit-memory-hub/speckit.memory-md.prepare-context.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.00365 |
| Opus 5 | $0.00010 | $0.00182 |
| Sonnet 5 | $0.00004 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
speckit.memory-md.prepare-context 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 9d 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.
What it actually says
Prepare Context
Use this command to prepare the technical and historical context for the current task. It handles first-time setup, incremental refresh, and post-upgrade scenarios automatically through MCP cache tools.
Usage
Run this command by providing the feature directory and an optional search query.
/speckit.memory-md.prepare-context --feature specs/<feature> --query "<optional_search_terms>"
MCP-Managed Flow
Use MCP tools for the full cache lifecycle:
- Refresh Cache: Call
speckit_memory_refresh_cache(scope="all"). - Search Memory (Optional): If a custom query is provided, call
speckit_memory_search(query="<query>"). - Memory Synthesis: Call
speckit_memory_synthesize(feature="specs/<feature>", query="<optional query>"). - Doc Synthesis: Call
speckit_memory_synthesize_docs(feature="specs/<feature>"). - Read Results: Read the returned
memory-synthesis.mdanddoc-synthesis.mdoutput paths.
Token Banner: Show the baseline / cached / saved token summary after the synthesis step so the savings stay visible during normal runs.
Orchestration Note
This command is automatically executed by spec-kit-architecture-guard as part of its governed-* workflows. Manual execution is optional and typically only necessary if you need to refresh context or synthesis results outside of a formal governed turn.
Goal
Ensure the agent has the latest "Why" and "How" from durable memory before proposing any changes or review findings.
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.
- 9d ago First seen · 36 lines · 19 tokens per session scan A 6fb3ff589fae
speckit.memory-md.prepare-context is a command published in the GitHub repository DyanGalih/spec-kit-memory-hub (15 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 365 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
wiki-query
Ask questions against the wiki. Synthesizes answers from wiki pages with cross-reference citations.
wiki-req
Capture and decompose a concept into atomic, traceable wiki requirements. Clarifies ambiguous requirements, splits them into atomic pieces, and persists them as wiki/requirements/ pages with status tracking.
wiki-retro
Save an atomic insight from the current task into the wiki. Creates a single markdown file that layered recall surfaces in future sessions.
wiki-discover
Auto-discover new sources from the web. Searches based on config topics and known knowledge gaps.
wiki-init
Initialize a new LLM Wiki in the current directory. Creates the full directory structure, config, and template files.
wiki-run
Run the full wiki cycle: discover → ingest → lint. Optionally schedule for auto-updates.