Borrowing it
Nothing to install: this file belongs to auerbachb/claude-code-config. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/auerbachb/claude-code-config/main/.claude/skills/recap/SKILL.mdgit clone --depth 1 https://github.com/auerbachb/claude-code-configWrote 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/auerbachb/claude-code-config/recap)<a href="https://agentmods.dev/skills/auerbachb/claude-code-config/recap"><img src="https://agentmods.dev/badge/skills/auerbachb/claude-code-config/recap/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/skills/auerbachb/claude-code-config/recap"><img src="https://agentmods.dev/badge/skills/auerbachb/claude-code-config/recap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 14 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
- medium Agent Snooping · line 287 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 336 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Rogue Agent · line 336 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00042 | $0.05591 |
| Opus 5.5 | $0.00017 | $0.02236 |
| Sonnet 5.5 | $0.00008 | $0.01118 |
| Haiku 4.5 | $0.00004 | $0.00559 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 337 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Produce a functional-improvement summary of a PR or issue: what the work did (a merged/open PR) or hopes to do (an open issue), written for a technical collaborator who wants the feature perspective — not the implementation walkthrough.
/recap is the single-target companion to /standup. /standup rolls up all recent activity across a time window for a daily report; /recap zooms in on one PR or issue and renders its functional story as nested bullets (or a table). Reach for /standup for "what happened lately"; reach for /recap for "explain this one PR/issue to my collaborator."
Output modes
| Mode | Flag | Effect |
|---|---|---|
| Nested bullets | (default) | Top-level bullet = functional change; sub-bullets = scope/notes |
| Table | --table |
Markdown table with Change | Notes columns |
| Full | --full |
Relax the word budget; keep nested-bullet (or table) structure |
| Technical | --technical |
Add a second tier of detail per bullet (mechanism, files, key endpoints) without removing the conversational top-level bullet |
| Executive | --executive |
Add a leadership read on top of the functional summary: what the change advances strategically, what it risks, and how confident the read is |
Flags compose: --table --technical adds a third "Technical detail" column; --full --technical keeps both expansions. --executive composes with all three — it appends its block after the normal output (or its rows/note under the table) rather than replacing anything.
Step 1: Parse arguments and flags
Parse $ARGUMENTS. Extract flags first, then interpret whatever remains as the target identifier.
- Flags (any order, anywhere in
$ARGUMENTS):--table,--full,--technical,--executive. Set a boolean for each; strip them from the argument string. - Target identifier — take the first non-flag token only (see batch handling below). It is one of:
- URL (
https://github.com/<owner>/<repo>/pull/123or.../issues/123) → extract both the<owner>/<repo>and the trailing number; the path segment (/pull/vs/issues/) fixes the type. The owner/repo from the URL must qualify every laterghcall (--repo <owner>/<repo>) — otherwise a URL for another repo would silently recap whatever item shares that number in the current repo. #Nor bare number (452,#457) → strip any leading#; target the current repo; type is not yet known (resolve in Step 2).- Empty → auto-detect (see below).
- URL (
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 Changed · +81 lines e3dad2dc724c
- 2mo ago First seen · 256 lines · 42 tokens per session scan A 58d11751f22a
recap is a skill published in the GitHub repository auerbachb/claude-code-config (5 stars, last pushed 2d ago), licensed MIT. It adds 42 tokens to every session and 5,591 once invoked, about $0.0002 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 skills, from other repositories
skeptic
Adversarial reviewer for Bug Hunter. Challenges each behavioral finding against actual code, checks defenses, and preserves unresolved cases for independent review.
referee
Final arbiter for Bug Hunter. Independently verifies behavioral findings, resolves Skeptic challenges, and calibrates severity and confidence.
commit-security-scan
Scan code changes for security vulnerabilities using Bug Hunter-native artifacts and STRIDE context. Use whenever the user asks for PR security review, commit-diff scanning, staged-change security checks, branch-comparison security review, or pre-merge security analysis of changed code.
robin
Use whenever an agent creates, updates, reviews, or completes a GitHub pull request. Detect whether Robin is installed in the repository; when it is, automatically drive the PR through a bounded review, verified-fix, reply, thread-resolution, re-review, authorized-merge, and cleanup loop without requiring the user to…
adr
Create and manage Architecture Decision Records. Documents significant technical decisions with context, alternatives, and consequences. Also supports evaluate (assess proposals) and design (system design) modes.
deploy-checklist
Pre-deployment verification checklist. Generates customized checklists based on tech-stack with rollback triggers. Auto-invoked by /draft:upload.