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/saffron-health/opencode-gui/wrap_upgit clone --depth 1 https://github.com/saffron-health/opencode-guiWhat 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.00245 |
| Opus 5 | $0.00000 | $0.00122 |
| Sonnet 5 | $0.00000 | $0.00049 |
| Haiku 4.5 | $0.00000 | $0.00024 |
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 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.
What it actually says
Wrap up the current work session by committing changes, ensuring a PR exists, and providing a handoff summary for the next developer.
Process
- Check branch: If on main, checkout a new branch with descriptive name based on work done
- Review conversation: Summarize what was worked on during this session
- Check bead status: Run
bd list --jsonto see which issues were touched - Commit changes: Create commit with descriptive message based on work done
- Check for PR: Use
gh pr list --head <current-branch>to see if PR exists - Create or update PR:
- If no PR exists: Create one with
gh pr createusing appropriate title and description - If PR exists: Query current title/description with
gh pr view <number>, update if needed withgh pr edit
- If no PR exists: Create one with
- Push changes: Push commits to remote branch
- Generate handoff: Create summary containing:
- What was accomplished this session
- What was started but not finished
- PR link and status
- Key decisions and context from this session
- Next steps with recommended approach
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 · 20 lines · 0 tokens per session scan A 404c48dcca73
wrap_up is a command published in the GitHub repository saffron-health/opencode-gui (57 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 245 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
pr-submit
Create git commit and submit current branch with Graphite (squashes commits and rebases stack).
ship
Commit all changes, push branch, create/update PR, and run local validation.
speckit.aftercode
Automatically execute the subsequent code delivery pipeline: skilltypesync → changelog → commit → prgenerate, in strict sequential order.
commit-push-pr
Commit, push, and open a PR.
ship
Create a new git branch, commit changes, and create a pull request.
ship
Ship: review gate, tests, version bump, changelog, conventional commit, docs update, PR. Complete pipeline from done to merged.