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/nodnarbnitram/claude-code-extensions/wrapup-skillupgit clone --depth 1 https://github.com/nodnarbnitram/claude-code-extensionsWhat 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.00014 | $0.01004 |
| Opus 5 | $0.00007 | $0.00502 |
| Sonnet 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 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.
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.
- 2d 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 4mo ago), licensed MIT. It adds 14 tokens to every session and 1,004 once invoked, about $0.0001 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-30.
Other commands, from other repositories
claude-flow-swarm
Coordinate multi-agent swarms for complex tasks.
advisor
Advisory gate for triage or plan decisions. Spawns a second-opinion agent that challenges assumptions, surfaces risks, and proposes alternatives before the decision commits. Based on Anthropic advisor tool pattern.
bootstrap
PACT session-start ritual — identify the session team (platform-provisioned), secretary spawn, paused-state surface, bootstrap marker.
ox-session-review
Command "ox-session-review" from sageox/ox, covering failure-mode watch-list (read first), from the ledger root. should print 0, phase 1 — scan & score (read-only), quality buckets (first match wins) and removal candidates.
add-agent
引导新增一个 Agent 适配器。用法 /add-agent.
migrate
Command "migrate" from chohra-med/expo_boilerplate, covering invocation, steps and rule.