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.
git clone --depth 1 https://github.com/nodnarbnitram/claude-code-extensionsWrote 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/nodnarbnitram/claude-code-extensions/wrapup-skillup)<a href="https://agentmods.dev/commands/nodnarbnitram/claude-code-extensions/wrapup-skillup"><img src="https://agentmods.dev/badge/commands/nodnarbnitram/claude-code-extensions/wrapup-skillup/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/commands/nodnarbnitram/claude-code-extensions/wrapup-skillup"><img src="https://agentmods.dev/badge/commands/nodnarbnitram/claude-code-extensions/wrapup-skillup.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00014 | $0.01004 |
| Opus 5.5 | $0.00006 | $0.00402 |
| Sonnet 5.5 | $0.00003 | $0.00201 |
| Haiku 4.5 | $0.00001 | $0.00100 |
Grade A, and why
wrapup-skillup 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Wrapup & Skillup
Generate a session report for topic: $ARGUMENTS
Your Task
Analyze this conversation session and create a comprehensive report that captures learnings, documents pitfalls, and recommends extensions that could help in future similar sessions.
Instructions
- Analyze the session context - Review the entire conversation from start to finish
- Extract the original request - Identify the first user message that started this session
- Summarize tool usage - Document which tools were used, how, and why
- Identify key learnings - What discoveries, patterns, or insights emerged?
- Document pitfalls - What problems were encountered? How were they resolved?
- Note outcomes - What was accomplished?
- Find ticket references - Look for any Linear, GitHub, or other ticket IDs mentioned
- Recommend extensions - Based on the session, suggest which extension types would be most valuable
Output Format
Write the report to: .claude/session-reports/YYYY-MM-DD-HH-MM-{topic}.md
Where {topic} is the topic-slug argument (use "session" if not provided).
Use this template structure:
# Session Report: {Topic Title}
## Metadata
- **Date**: YYYY-MM-DD HH:MM
- **Duration**: ~X minutes (estimate based on conversation length)
- **Related Tickets**: [ticket-ids or "None"]
## Original Request
> [Quote the first user message that initiated this session]
## Tools Used
| Tool | Purpose | Key Usage |
|------|---------|-----------|
| Tool1 | Why it was used | How it was applied |
| Tool2 | Why it was used | How it was applied |
## Key Learnings
- **Learning 1**: Description of what was discovered
- **Learning 2**: Description of pattern identified
- **Learning 3**: Description of insight gained
## Pitfalls & Solutions
### Pitfall: [Issue Name]
- **Problem**: What went wrong or was difficult
- **Solution**: How it was resolved
- **Prevention**: How to avoid this in the future
### Pitfall: [Another Issue]
- **Problem**: Description
- **Solution**: Resolution
- **Prevention**: Future avoidance strategy
## Results & Outcomes
- **Outcome 1**: What was accomplished
- **Outcome 2**: What was delivered
- **Files Changed**: List key files created or modified
## Extension Recommendations
Based on this session, the following extensions would help in similar future work:
### Recommended: [Skill/Command/Hook/Agent]
**Name**: `suggested-name`
**Purpose**: Why this extension would be valuable
**Type Justification**: Why this type (skill vs command vs hook vs agent) is appropriate
**Template**:
```yaml
---
name: suggested-name
description: Description for discovery
---
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 First seen · 142 lines · 14 tokens per session scan A 2a717f77a678
wrapup-skillup is a command published in the GitHub repository nodnarbnitram/claude-code-extensions (16 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 1,004 once invoked, about $0.0001 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-30.
Other commands, from other repositories
cancel-ralph
Cancel active Ralph Loop.
engage.actions
Execute Phase 7 - Actions on Objectives and Goal Achievement.
quickstart
Interactive onboarding guide — set up credentials, connect to orq.ai, and learn every command and skill.
r
Resume the last handoff and carry on with the outstanding work.
focus
You are an ADHD focus assistant. Help the user commit to ONE task and block mental distractions.
stuck
You are an ADHD-friendly unblocking assistant. Help users get unstuck when they don't know what to do.