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 skills/control-decks/think-it-through/recapnpx skills add control-decks/think-it-through --skill recapgit clone --depth 1 https://github.com/control-decks/think-it-throughWrote 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/skills/control-decks/think-it-through/recap)<a href="https://agentmods.dev/skills/control-decks/think-it-through/recap"><img src="https://agentmods.dev/badge/skills/control-decks/think-it-through/recap.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 | $0.00049 | $0.00324 |
| Opus 5 | $0.00024 | $0.00162 |
| Sonnet 5 | $0.00010 | $0.00065 |
| Haiku 4.5 | $0.00005 | $0.00032 |
Grade A, and why
recap 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 5d 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
🗺️ Think Recap
ID: think-it-through/recap
HACP: 0.4
Kind: operation
Mode: transform
Traits: read-only, semantic
Default Binding: Full available conversation
Accepts: hacp/content, hacp/result
Produces: think-it-through/conversation-map
Duration: once
Effect: Reconstruct Conversation → Topics → Axes with concise reusable
human labels, classify their contents and states, then synthesize relationships
across them.
Limits: Preserve uncertainty and disagreement. Do not suggest another command, choose, decide, plan, create technical identifiers, persist state, or create a file.
Format
Begin the combo trace with > 🎯 **<binding>** → 🗺️ **RECAP**, followed by Map and Digest. Show the Conversation → Topics → Axes tree and the state of each axis. Give every topic and axis a concise label the user can repeat with on-topic or on-axis.
Add an output with → and presentation cards with +. Do not append suggested commands.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 32 lines · 49 tokens per session scan A a51cd811e5c4
recap is a skill published in the GitHub repository control-decks/think-it-through (3 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 324 once invoked, about $0.0002 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 skills, from other repositories
codex-memory-trim
Manage Codex's native global memory (/.codex/memories) with three sub-procedures - trim (audit + dedupe + three-layer cleanup), compress (rewrite verbose memories into concise form), and add-global (add a custom global rule/preference). Use when the user asks to 精简/清理/整理/压缩 Codex 记忆, 去重, 简化冗长记忆, 添加/写入/修改全局记忆 or a…
codex-memory-curator
Audit, review, clean up, and prune Codex memories. Use when the user asks about /.codex/memories, stale or noisy memories, memory pollution, cross-repo rule leakage, sensitive memory contents, memory config tuning, cleanup plans, or whether entries belong in memory, AGENTS.md, repo docs, skills, config, or deletion.…
claude-memory-curator
Audit, review, clean up, and prune Claude Code durable context. Use when the user asks about CLAUDE.md, CLAUDE.local.md, .claude/rules, user Claude rules, Claude Code auto memory, /memory, stale instructions, memory pollution, sensitive context, settings such as autoMemoryEnabled or claudeMdExcludes, or where a Claude…
cursor-memory-curator
Audit, review, clean up, and prune Cursor durable context. Use when the user asks about Cursor rules, .cursor/rules, .cursorrules, User Rules, Team Rules, Cursor memory-bank artifacts, stale or noisy persistent context, rule conflicts, sensitive rule contents, or why Cursor keeps forgetting or using old guidance. Do…
session-memory-handoff
Начни, веди и заверши исследовательскую сессию с Git-операционной памятью: branch/worktree, session note, смысловые commits, CURRENT.md и handoff. Используй для параллельных/долгих задач; не используй для одношаговой задачи без durable state и не делай автоматический push.
codex-context-guard
Prevent Codex context-window exhaustion during long-running refactors, repo audits, migrations, debugging sessions, or tasks with large logs, many file reads, or repeated tool output. Use when Codex context is getting high, /compact may be needed, or the user asks for context-efficient workflows.