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 skills/jonathanmalkin/jules/wrap-upnpx skills add jonathanmalkin/jules --skill wrap-upgit clone --depth 1 https://github.com/jonathanmalkin/julesWrote 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/jonathanmalkin/jules/wrap-up)<a href="https://agentmods.dev/skills/jonathanmalkin/jules/wrap-up"><img src="https://agentmods.dev/badge/skills/jonathanmalkin/jules/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.1 | $0.00078 | $0.02210 |
| Opus 5 | $0.00039 | $0.01105 |
| Sonnet 5 | $0.00016 | $0.00442 |
| Haiku 4.5 | $0.00008 | $0.00221 |
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 6d 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 — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wrap-Up
Use this at the end of a meaningful conversation or when the user asks to ship, close out, commit, push, or prepare a handoff.
The job is not just repo cleanup. The job is to leave the workspace in a known state, avoid stepping on running schedulers, ship only intentional changes, and turn repeated friction into improvement candidates.
Opening
Start with Workflow: wrap-up. Then run the deterministic preflight before
making any changes:
python3 ~/.agents/skills/workflows/wrap-up/scripts/wrapup_preflight.py --workspace "$PWD" --due-window-minutes 90
If this skill is running from a copied surface where ~/.agents is unavailable,
run the copy-local script at scripts/wrapup_preflight.py.
Core Sequence
Run these phases in order.
1. Outcome State
Summarize the session's original objective and current state:
- what got done
- what did not get done
- whether the work changed scope
- whether the handoff is
CompleteorContinues
Do not call the session complete if the stated objective is unfinished.
2. Scheduler-Safe Preflight
Use the preflight script output as the collision map. At minimum, account for:
- user LaunchAgents in
~/Library/LaunchAgents - user crontab from
crontab -l - Hermes cron jobs in
~/.hermes/profiles/*/cron/jobs.json - Codex automations in
~/.codex/automations/*/automation.toml - running Hermes gateways, dashboards, WebUI, Dev Secrets, history-search, and other launchd-managed services when visible
Default safety rules:
- Do not restart, unload, kickstart, repair, or create background services during normal wrap-up.
- Do not edit LaunchAgents, Hermes
config.yaml, Hermescron/jobs.json, secrets runtime files, scheduler scripts, or automation definitions unless the session explicitly touched scheduler work. - Treat scheduler output, logs, state snapshots, lock files, and generated reports as owned by running processes unless they are part of this session's deliverable.
- If a scheduled job is unhealthy, record it as an improvement candidate unless the user explicitly asked for scheduler repair.
- If a job is due soon, avoid broad staging. Stage only files known to belong to this session.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 299 lines · 78 tokens per session scan A b2d478a7a057
wrap-up is a skill published in the GitHub repository jonathanmalkin/jules (65 stars, last pushed 3mo ago), licensed MIT. It adds 78 tokens to every session and 2,210 once invoked, about $0.0004 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…