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.
npx agentmods add commands/daveangulo/twining-mcp/twining-exportgit clone --depth 1 https://github.com/daveangulo/twining-mcpWhat 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 | $0.00017 | $0.00192 |
| Opus 5 | $0.00009 | $0.00096 |
| Sonnet 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 2d 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.
- 2d 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 6d ago), licensed MIT. It adds 17 tokens to every session and 192 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-31.
Other commands, from other repositories
riskreview
The user invoked the /riskreview facade command from the risk-review-pipeline pack.
export
Export a knowledge abstract to an Obsidian vault — a folder of Markdown notes linked by [[wikilinks]].
wh:graph-review
Use when you want a Wheeler graph quality audit (wrong types, broken paths, dupes, stale nodes) with suggested fixes.
wh:asta-lit
Use when the user wants to find literature with Asta Paper Finder and ingest the results into the Wheeler knowledge graph.
memory-search
Search agent memory + learned patterns for cross-session context relevant to $ARGUMENTS.
bootstrap-memory
RUN { git ls-files; git ls-files --others --exclude-standard; } 2>/dev/null | sort -u | xargs wc -l 2>/dev/null | sort -rn | head -150 READ README.md.