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/ackeskin/contexture/recapgit clone --depth 1 https://github.com/AcKeskin/contextureWhat 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.00031 | $0.00260 |
| Opus 5 | $0.00015 | $0.00130 |
| Sonnet 5 | $0.00006 | $0.00052 |
| Haiku 4.5 | $0.00003 | $0.00026 |
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 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
Run the recap skill for the current session.
Any text after /recap is treated as a short title for the recap. Examples:
/recap— infer title from the session's primary goal./recap session-recaps— use that as the title/slug./recap auth middleware rewrite— free-form prose title; skill slugs it.
The skill gathers the session's context (files touched, commits produced, corrections and decisions, learnings, pending work), drafts a full recap (frontmatter + structured body), and shows it for user confirmation. Accept / edit / reject. On accept, the file lands under ~/.claude/projects/<slug>/memory/sessions/YYYY-MM-DD-<slug>.md and a promotion pass offers to capture non-trivial Learned items as rule-tier memories.
Never auto-fires. Mode B (silent session-end capture) is parked — every recap is explicit and user-confirmed.
See ~/.claude/skills/recap/SKILL.md for the full procedure.
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 · 18 lines · 31 tokens per session scan A dca0b6a0249a
recap is a command published in the GitHub repository AcKeskin/contexture (2 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 260 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 commands, from other repositories
atomic-commits
Analyze staged changes and organize them into intuitive atomic commits following conventional commits.
address
Address code review feedback — corroborate, validate, and implement changes from a review's final.md.
translate-review-to-single-human
Translate a multi-reviewer code review into a single human-voice GitHub PR comment.
doctor
Check OCR installation and verify all dependencies are available.
map
Generate a Code Review Map to help navigate large, complex changesets.
post
Post the current OCR review to a GitHub PR.