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 cyanheads/medical-codes-mcp-server --skill git-wrapupgit clone --depth 1 https://github.com/cyanheads/medical-codes-mcp-serverWrote 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/cyanheads/medical-codes-mcp-server/git-wrapup)<a href="https://agentmods.dev/skills/cyanheads/medical-codes-mcp-server/git-wrapup"><img src="https://agentmods.dev/badge/skills/cyanheads/medical-codes-mcp-server/git-wrapup/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/cyanheads/medical-codes-mcp-server/git-wrapup"><img src="https://agentmods.dev/badge/skills/cyanheads/medical-codes-mcp-server/git-wrapup.svg" alt="Reviewed on agentmods" width="80" 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.00109 | $0.08132 |
| Opus 5.5 | $0.00044 | $0.03253 |
| Sonnet 5.5 | $0.00022 | $0.01626 |
| Haiku 4.5 | $0.00011 | $0.00813 |
Grade A, and why
git-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 yesterday.
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.
This is a copy
100% identical to git-wrapup — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 349 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
Working-tree or staged changes are ready to ship as a new version. This skill lands them as a stack of logical commits — the work grouped by concern, topped by a release commit (version + changelog + tree). It does NOT tag, push to main, or publish — release-and-publish does all three.
Common triggers:
- Feature work, bug fixes, or dependency updates are done and tested
- A maintenance or polish pass left changes in the working tree
- An orchestrator says "wrapup this project"
Release PR mode
A project can route every release through a pull request — one PR per version, for the audit trail and a stable review target. The mode is declared in the project's CLAUDE.md/AGENTS.md or in the caller's brief; when neither says anything, there is no release PR and the stack lands on main directly.
| Mode | Wrapup ends at | Then |
|---|---|---|
| (none — default) | commit stack on main, tree clean |
release-and-publish tags HEAD and ships |
| gated | commit stack on release/<version>, branch pushed, PR open |
a review pass on the PR (release-pr-review skill), then a separate release-and-publish run fast-forwards main, tags, and ships |
| straight-through | same as gated | the same agent continues straight into release-and-publish |
Create release/<version> as soon as the version is known, before any commit; a caller-pinned version permits branching before step 1. Every work and release commit lands on that branch. If commits were accidentally made on an unpushed main, create the release branch at HEAD and continue without moving main; never reset, force a branch ref, or rewrite history. If those commits were already pushed to main, report the state before proceeding. The commit stack, release commit, and tag format are identical in every mode — the PR adds an audit artifact.
Pre-wrapup gate checklist
Every item must be true before starting wrapup. Committing means releasing — a commit only happens when the work is ready to ship, not just "the edits are done." Each item is a goal to verify.
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.
- yesterday Changed 45156f3bb624
- 4d ago Changed · +29 lines · -11 tokens per session fef170c6be4f
- 20d ago Changed · +11 lines 02ceed0255d0
- 1mo ago Changed · +62 lines · +38 tokens per session 37214bd314b3
- 2mo ago First seen · 247 lines · 82 tokens per session scan A eadc76d1a313
git-wrapup is a skill published in the GitHub repository cyanheads/medical-codes-mcp-server (2 stars, last pushed today), licensed Apache-2.0. It adds 109 tokens to every session and 8,132 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to git-wrapup, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
commit-pr
Mandatory Codex/Copilot publication adapter for opencode-swarm. Use for every GitHub issue assignment that results in code changes, commits, pushes, draft PRs, PR body edits, PR readying, release notes, or CI closeout. Must be loaded before git push, gh pr create, gh pr edit, or gh pr ready. Routes to the single…
contributing
Codex adapter for the opencode-swarm contribution checklist. Use when preparing user-visible changes, release note fragments, local validation, branch hygiene, PR checklist items, or contribution-policy compliance before publishing work.
git
Run git version control commands for repository management. Use when the user asks to check status, view history or diffs, stage and commit changes, manage branches, merge or rebase, work with remotes, stash changes, tag releases, cherry-pick commits, bisect regressions, resolve conflicts, manage worktrees or…
studio-source-control
Drive a scoped application's linked git repository from the instance — what has to be true before Source Control works at all, the commit-then-push order, stashes and branches over /api/snsourcecontrol, and when this replaces update sets rather than sitting next to them.
github-cli
Skill "github-cli" from juan294/cc-rpi, covering github cli, json field discovery, pr check interpretation, or watch existing checks to completion and release vs pr flags.
datalad
Retrieve, version, and publish scientific datasets with DataLad and git-annex, and capture computational provenance with datalad run, rerun, and containers-run. Use when cloning or fetching data from OpenNeuro, DANDI, datasets.datalad.org, or any DataLad dataset; when a file in a dataset reads as a broken symlink or a…