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/gzupark/claude-plugin-pack/recapgit clone --depth 1 https://github.com/GzuPark/claude-plugin-packWrote 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/commands/gzupark/claude-plugin-pack/recap)<a href="https://agentmods.dev/commands/gzupark/claude-plugin-pack/recap"><img src="https://agentmods.dev/badge/commands/gzupark/claude-plugin-pack/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.00006 | $0.00935 |
| Opus 5 | $0.00003 | $0.00467 |
| Sonnet 5 | $0.00001 | $0.00187 |
| Haiku 4.5 | $0.00001 | $0.00093 |
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 3d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Work Recap Command
Analyze the session and organize documentation updates, automation suggestions, learning records, and follow-up tasks.
Input
$1: (Optional) User request. Additional context or focus area for the analysis.
Execution Flow
Step 1: Check Git Status
git status
git diff --stat
Check if there are any changes.
Early Exit: If there are no staged/unstaged changes and no untracked files, inform the user "No changes to analyze" and end.
Step 2: Prepare Session Context
Identify important turns in the current session:
- Turns where AskUserQuestion was used (user decisions)
- Include the last 15 turns by default
- Include important turns regardless of their position
Prepare session summary:
- Tasks performed
- Files modified
- Key decisions made
Step 3: Phase 1 - Parallel Analysis
Run 4 agents in parallel. Use the Task tool to execute them simultaneously:
Task 1: doc-updater agent
- Pass session context
- Collect CLAUDE.md, context.md update suggestions
Task 2: automation-scout agent
- Pass session context
- Detect automation opportunities from repetitive patterns
Task 3: learning-extractor agent
- Pass session context
- Extract TIL (Today I Learned) items
Task 4: followup-suggester agent
- Pass session context
- Organize incomplete tasks and next priorities
Important: The 4 agents are independent, so they MUST be run in parallel.
Step 4: Phase 2 - Duplicate Validation
After collecting Phase 1 results, run the duplicate-checker agent:
Task: duplicate-checker agent
- Pass all suggestions from Phase 1
- Compare with current project's CLAUDE.md, context.md, .claude/
- Filter duplicate items
Step 5: Results Integration and Display
Display results grouped by action:
## Work Recap Analysis Complete
### Documentation Updates
- CLAUDE.md: N items suggested
- [Item 1 summary]
- [Item 2 summary]
- context.md: N items suggested
- [Item 1 summary]
### Automation Opportunities
- N automation suggestions
- [Type] [Name]: [Description]
### Learning Records (TIL)
- N items
- [Item 1]
- [Item 2]
### Next Steps
- P0: [Urgent task]
- P1: [High priority]
- P2: [Medium priority]
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.
- 3d ago First seen · 165 lines · 6 tokens per session scan A 936ca8d2712e
recap is a command published in the GitHub repository GzuPark/claude-plugin-pack (6 stars, last pushed 7mo ago), licensed MIT. It adds 6 tokens to every session and 935 once invoked, about $0.0000 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.