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 skills add drn/dots --skill wrapupgit clone --depth 1 https://github.com/drn/dotsWrote 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/drn/dots/wrapup)<a href="https://agentmods.dev/skills/drn/dots/wrapup"><img src="https://agentmods.dev/badge/skills/drn/dots/wrapup.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.00057 | $0.01153 |
| Opus 5 | $0.00028 | $0.00576 |
| Sonnet 5 | $0.00011 | $0.00231 |
| Haiku 4.5 | $0.00006 | $0.00115 |
Grade A, and why
wrapup 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 3d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Wrapup
End-of-session sweep that detects loose ends and routes to the right follow-up actions before you close the conversation.
Context
- Current branch: !
git branch --show-current - Base ref: !
git branch -r 2>/dev/null | grep -oE 'origin/(main|master)' | head -1 - Uncommitted changes: !
git status --short 2>/dev/null | head -20 - Unpushed commits vs main: !
git log origin/main..HEAD --oneline 2>/dev/null | head -20 - Unpushed commits vs master: !
git log origin/master..HEAD --oneline 2>/dev/null | head -20 - Open PRs (mine): !
gh pr list --author @me --state open 2>/dev/null | head -10 - Stash list: !
git stash list 2>/dev/null | head -5 - Knowledge base exists: !
ls context/knowledge/index.md 2>/dev/null | head -1 - Context directory exists: !
ls context/ 2>/dev/null | head -5
Instructions
Do NOT automatically run any of the suggested skills. Present the full report first, then let the user pick which actions to take.
Run through each check below. For each one that fires, report the finding and suggest the action. At the end, present a summary with recommended next steps.
Check 1: Uncommitted Changes
If git status shows modified, added, or untracked files:
- List the changed files
- Suggest: Commit the changes, or stash if the work is incomplete
- If the changes look ready: offer to run
/commit
Check 2: Unpushed Commits
If the branch has commits ahead of the remote base branch:
- Show the commit count and titles
- Suggest: Push to remote, or open a PR via
/pr
Check 3: Unmerged Branch
If the current branch is not the main branch and has commits:
- Note the branch name and commit count
- Check if a PR already exists for this branch (from the Open PRs context)
- If PR exists: report its status (open, draft, checks passing/failing)
- If no PR exists: suggest opening one via
/pr - If the work is incomplete: suggest generating a
/handofffor the next session
Check 4: Open PRs Needing Attention
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.
- 3d ago First seen · 128 lines · 57 tokens per session scan A 14b131a308c2
wrapup is a skill published in the GitHub repository drn/dots (23 stars, last pushed 2d ago), licensed MIT. It adds 57 tokens to every session and 1,153 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".