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.capture-from-diff)<a href="https://agentmods.dev/commands/dyangalih/spec-kit-memory-hub/speckit.memory-md.capture-from-diff"><img src="https://agentmods.dev/badge/commands/dyangalih/spec-kit-memory-hub/speckit.memory-md.capture-from-diff.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.1 | $0.00013 | $0.01391 |
| Opus 5 | $0.00006 | $0.00696 |
| Sonnet 5 | $0.00003 | $0.00278 |
| Haiku 4.5 | $0.00001 | $0.00139 |
Grade A, and why
speckit.memory-md.capture-from-diff 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 8d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Capture From Diff
You are capturing durable knowledge for memory-hub by analyzing code changes.
Resolve configuration first. Use .specify/extensions/memory-md/config.yml when present; otherwise default to memory_root: docs/memory and specs_root: specs.
Capture is automatic based on your confidence score. Evaluate the proposed durable memory and determine your confidence (0-100%) that it is correct, durable, and non-duplicate. If your confidence is > 50%, automatically approve the capture and register it. If your confidence is <= 50%, ignore it and do not capture. However, you must always allow the user to trigger this manually and bypass the confidence check if they explicitly request a capture.
Determine Review Scope
- Identify Changed Files:
- If the user provided a diff or explicit instructions, follow them.
- Otherwise, you MUST execute the platform-appropriate script with
--jsonto detect changed files since the merge-base or in the working directory.- Linux/macOS: run the script at
scripts/bash/detect-changed-files.sh --json - Windows: run the script at
scripts/powershell/detect-changed-files.ps1 --json - When invoked via a Spec Kit command context that resolves
{SCRIPT}, use the provided value directly.
- Linux/macOS: run the script at
- Use the
changed_fileslist as the primary set for knowledge extraction.
Durable Memory Context (Duplicate Prevention)
Before proposing new entries, check the existing memory to avoid duplicates.
- Refresh Cache: If memory search is empty or you need the latest state, call
speckit_memory_refresh_cache(scope="memory")ornpx speckit-memory refresh-memoryto restore the SQLite cache from the backup.mdfiles. - Targeted Search: Call
speckit_memory_search(query="architecture constraints boundaries decisions <topic>")for candidate topics identified from the diff. - Read Results: Review the search results to ensure the candidate lesson is not already captured.
- Do NOT read
.mdmemory files directly. MCP search results via SQLite are the single source of truth. The.mdfiles are only backups managed by the extension.
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.
- 8d ago First seen · 112 lines · 13 tokens per session scan A a15951c1c175
speckit.memory-md.capture-from-diff is a command published in the GitHub repository DyanGalih/spec-kit-memory-hub (15 stars, last pushed 3mo ago), licensed MIT. It adds 13 tokens to every session and 1,391 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.