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/daveangulo/twining-mcpWrote 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/daveangulo/twining-mcp/twining-export)<a href="https://agentmods.dev/commands/daveangulo/twining-mcp/twining-export"><img src="https://agentmods.dev/badge/commands/daveangulo/twining-mcp/twining-export/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/daveangulo/twining-mcp/twining-export"><img src="https://agentmods.dev/badge/commands/daveangulo/twining-mcp/twining-export.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.00017 | $0.00192 |
| Opus 5.5 | $0.00007 | $0.00077 |
| Sonnet 5.5 | $0.00003 | $0.00038 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
twining:export 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.
What it actually says
Ask the user for the scope to export (default: entire project). Then run twining_export with that scope.
twining_export requires tools.full_surface: true in .twining/config.yml. If it is unavailable, say so plainly and offer twining_assemble (scoped briefing) or twining_status (health summary) instead — do not fabricate an export.
Present the exported markdown, which includes:
- All blackboard entries in scope
- All decisions with full rationale and alternatives
- Knowledge graph entities and relations
This is useful for:
- Context window handoff — paste into a new session to continue work with full history
- Documentation — snapshot of architectural decisions and coordination state
- Debugging — understanding what agents have done and why
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 · 19 lines · 17 tokens per session scan A 03650cc18a08
twining:export is a command published in the GitHub repository daveangulo/twining-mcp (7 stars, last pushed 13d ago), licensed MIT. It adds 17 tokens to every session and 192 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-31.
Other commands, from other repositories
search
Search decisions and checkpoints (semantic or list recent).
slm-profile
Memory profiles (separate namespaces inside one SuperLocalMemory store) and MCP tool sets (which tools your host sees). Use switchprofile or slm profile switch to change the active memory profile, the profileid argument to read or write another profile for one call, and slm tools set to choose the tool set every…
slm-bot-memory
Cross-bot memory on a shared computer (Grok Bot, Cursor plugin, any host where several agents share one machine). Explains agentid attribution vs. profile/scope access, how to namespace by agentid + profile + scope, and what must never be written to memory. Read this before the first remember/recall on a new…
slm-getting-started-bot
First-session orientation for SuperLocalMemory on a headless bot host (Grok Bot, or any Cursor-format plugin install with no hooks, no dashboard, and no interactive setup wizard). What is different here vs. Claude Code/Codex, which 19 tools are actually available, and the first three calls to make.
slm-scope
Controls memory visibility across profiles — personal (private, default), shared (selected profiles), or global (all profiles on this machine). Default is always personal. Only change scope when the user explicitly asks to share a memory across workspaces. Works with both remember (write scope) and recall (read scope…
memory-search
Search agent memory + learned patterns for cross-session context relevant to $ARGUMENTS.