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/liortesta/clawdagent/wrap-upgit clone --depth 1 https://github.com/liortesta/ClawdAgentWrote 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/liortesta/clawdagent/wrap-up)<a href="https://agentmods.dev/commands/liortesta/clawdagent/wrap-up"><img src="https://agentmods.dev/badge/commands/liortesta/clawdagent/wrap-up.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.00000 | $0.00305 |
| Opus 5 | $0.00000 | $0.00152 |
| Sonnet 5 | $0.00000 | $0.00061 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
wrap-up 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 4d 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
Session Wrap-Up
Consolidate learnings from this session and update project memory.
Process:
-
Summarize what was accomplished in this session:
- Features built
- Bugs fixed
- Decisions made
- Problems encountered
-
Update CLAUDE.md with any new:
- Architecture decisions (ADRs)
- Self-correction rules learned
- Project conventions discovered
- Key commands added
-
Check for loose ends:
- Any TODOs added during this session?
- Any tests marked as skipped?
- Any temporary code or workarounds?
- Any documentation that needs updating?
-
Create a handoff note — if someone (or a future Claude session) picks up where we left off, what do they need to know?
Output Format:
## Session Wrap-Up — [DATE]
### Accomplished
- [what was done]
### Decisions Made
- [decision]: [rationale]
### CLAUDE.md Updates
- [what was added/changed]
### Loose Ends
- [ ] [TODO or follow-up item]
### Handoff Note
[What the next session needs to know to continue effectively]
Rules:
- ALWAYS update CLAUDE.md — this is the persistent memory
- ALWAYS flag loose ends — don't let them get lost
- Keep the handoff note concise but complete
$ARGUMENTS
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.
- 4d ago First seen · 53 lines · 0 tokens per session scan A 4bc1c1e71eb4
wrap-up is a command published in the GitHub repository liortesta/ClawdAgent (11 stars, last pushed 7d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 305 tokens. 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
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
session-end
I'll summarize this coding session and update the memory system with our accomplishments.
memory-store
Store an insight, decision, or pattern to memory.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
neo-review
Get Neo's code review with semantic matching against past findings in memory. Use on a diff or module before merge, especially where earlier mistakes in this codebase are likely to recur. Skip for formatting, lint-catchable issues, and single-line changes.