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/hamchowderr/braynee/recapnpx skills add hamchowderr/braynee --skill recapgit clone --depth 1 https://github.com/hamchowderr/brayneeWhat 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.00094 | $0.00466 |
| Opus 5 | $0.00047 | $0.00233 |
| Sonnet 5 | $0.00019 | $0.00093 |
| Haiku 4.5 | $0.00009 | $0.00047 |
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
Recap Skill
Three modes: temporal (JSONL date scan), topic (QMD BM25), graph (session visualization). Every recap ends with One Thing — the single most impactful next action.
Usage
/recap yesterday
/recap last week
/recap 2026-05-01
/recap authentication bug
/recap company research
/recap graph last week
Workflow
See workflows/recap.md for routing logic.
Commands
# Temporal — list sessions by date
python3 {baseDir}/scripts/recap.py list yesterday
python3 {baseDir}/scripts/recap.py list "last week"
python3 {baseDir}/scripts/recap.py list "last 3 days"
# Expand a session
python3 {baseDir}/scripts/recap.py expand SESSION_ID
# Topic — QMD search with expansion
node ${CLAUDE_PLUGIN_ROOT}/scripts/qmd-wrapper.mjs search "QUERY"
node ${CLAUDE_PLUGIN_ROOT}/scripts/qmd-wrapper.mjs vsearch "QUERY"
# Graph
python3 {baseDir}/scripts/recap.py graph yesterday --out ~/Downloads/recap-graph.html
One Thing
After presenting results, synthesize:
- What has the most momentum right now?
- What's closest to done?
- What's blocked and needs a decision?
Output: one specific, actionable next step. Not generic ("work on project") — concrete ("finish the scaffold.py script for the setup skill").
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.
- 2d ago First seen · 61 lines · 94 tokens per session scan A 743b63a71e73
recap is a skill published in the GitHub repository hamchowderr/braynee (2 stars, last pushed 6d ago), licensed MIT. It adds 94 tokens to every session and 466 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.