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.repair-index)<a href="https://agentmods.dev/commands/dyangalih/spec-kit-memory-hub/speckit.memory-md.repair-index"><img src="https://agentmods.dev/badge/commands/dyangalih/spec-kit-memory-hub/speckit.memory-md.repair-index/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.repair-index"><img src="https://agentmods.dev/badge/commands/dyangalih/spec-kit-memory-hub/speckit.memory-md.repair-index.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.00314 |
| Opus 5 | $0.00010 | $0.00157 |
| Sonnet 5 | $0.00004 | $0.00063 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
speckit.memory-md.repair-index 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 11d 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
Repair Memory Index
Use this command when an older Memory Hub workflow may have removed valid docs/memory/INDEX.md rows, or when durable entries exist in docs/memory/**/*.md but are no longer discoverable through the index.
Source of Truth
SQLite is the primary operational cache. The Markdown memory files are the durable backups. INDEX.md is routing metadata for the backups and must not be pruned automatically.
MCP Flow
- Call
speckit_memory_repair_index(apply=false)first. - Review the proposed
missingRows. - If the proposed rows are valid, ask the user for approval.
- After explicit approval, call
speckit_memory_repair_index(apply=true). - Call
speckit_memory_searchif you need to verify the appended rows are now indexed.
Behavior
- Scans durable memory files for dated entries like
### YYYY-MM-DD - Title. - Detects entries missing from
INDEX.md. - Proposes compact routing rows with
recovered,needs-reviewtags. - Appends missing rows only when
apply=true. - Refreshes the SQLite memory cache after applying.
- Never deletes existing
INDEX.mdrows. - Never edits durable source entries.
Review Notes
Recovered rows should be reviewed later for better tags and clearer titles. The recovery step favors preserving discoverability over perfect metadata.
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.
- 11d ago First seen · 34 lines · 19 tokens per session scan A 51c600714949
speckit.memory-md.repair-index 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 314 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.