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.sync-shared)<a href="https://agentmods.dev/commands/dyangalih/spec-kit-memory-hub/speckit.memory-md.sync-shared"><img src="https://agentmods.dev/badge/commands/dyangalih/spec-kit-memory-hub/speckit.memory-md.sync-shared.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.00017 | $0.00384 |
| Opus 5 | $0.00009 | $0.00192 |
| Sonnet 5 | $0.00003 | $0.00077 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
speckit.memory-md.sync-shared 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 7d 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
Sync Shared Lessons
Query the global cross-project shared memory database for external lessons that match this project's technical profile, and synchronize them into a local review buffer.
This action is automatic based on your confidence score. Evaluate the necessity of syncing shared lessons based on the current context. If your confidence is > 50% that syncing is needed, automatically perform the sync. If your confidence is <= 50%, ignore it. However, you must always allow the user to trigger this manually if they explicitly request it.
Use this when:
- starting a new project and you want to pull in lessons from other projects using the same stack
- beginning a new sprint or major feature to leverage cross-project learnings
- you want to see what decisions or bug patterns other projects in your organization have documented
Tasks:
-
Confirm that the project is profiled (
speckit.memory-md.init-projecthas been run andproject_profileis configured inconfig.yml). -
Call
speckit_memory_sync_sharedto pull matching external memories from the global shared SQLite store (~/.spec-kit/shared-memory.sqlite). -
The sync operation will:
- Calculate the SHA-256 hash of the project's root path
- Search the global database for active lessons matching the language and framework
- Exclude any lessons that originated from this project itself to prevent redundancy
- Write all new external lessons into a reviewable markdown file at
docs/memory/SHARED_LESSONS.mdpre-populated with interactive banners
-
Guide the user to open and review
docs/memory/SHARED_LESSONS.md. Instruct them to merge any relevant findings into their permanentdecisions/orbugs/folders and delete the temporary review file.
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.
- 7d ago First seen · 29 lines · 17 tokens per session scan A c2a2076b538e
speckit.memory-md.sync-shared is a command published in the GitHub repository DyanGalih/spec-kit-memory-hub (15 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 384 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.