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/clinicaltrialsgov-mcp-server --skill git-wrapupgit clone --depth 1 https://github.com/cyanheads/clinicaltrialsgov-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/clinicaltrialsgov-mcp-server/git-wrapup)<a href="https://agentmods.dev/skills/cyanheads/clinicaltrialsgov-mcp-server/git-wrapup"><img src="https://agentmods.dev/badge/skills/cyanheads/clinicaltrialsgov-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/clinicaltrialsgov-mcp-server/git-wrapup"><img src="https://agentmods.dev/badge/skills/cyanheads/clinicaltrialsgov-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.00082 | $0.04142 |
| Opus 5 | $0.00041 | $0.02071 |
| Sonnet 5 | $0.00016 | $0.00828 |
| Haiku 4.5 | $0.00008 | $0.00414 |
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 10d 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.
This is a copy
100% identical to git-wrapup — 96 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 — 247 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) — with an annotated tag. It does NOT push or publish — that's a separate step (release-and-publish).
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"
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.
- Changes exist — uncommitted files or commits since the last tag
- Work is complete — no half-finished features, no "I'll add the test later," no TODO placeholders. The diff represents a shippable unit.
- Code simplified — if the diff spans more than ~50 changed lines or touches 3+ source files, the
code-simplifierskill has been run across the changes -
bun run devcheckpasses — typecheck + lint clean -
bun run rebuildsucceeds — full clean build from scratch - All tests pass —
bun run test:all(orbun run test), plusbun run test:packagewhere the project defines one: it guards the public-export manifest and is not part oftest:all. New tests and regression tests added as needed for the changes being shipped. - Fixes verified — bug fixes validated, generally via
bun run rebuildand field-testing. Not just written — confirmed to resolve the described behavior. - No known regressions — the changes don't break existing functionality
- GH issues updated — issues addressed by this work commented with what landed and any follow-ups needed. Concise. Backlinked as needed.
- Docs updated — surgical updates to existing docs as needed. New docs for new features. No large rewrites for documentation that's still accurate.
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.
- 10d ago First seen · 247 lines · 82 tokens per session scan A eadc76d1a313
git-wrapup is a skill published in the GitHub repository cyanheads/clinicaltrialsgov-mcp-server (91 stars, last pushed 7d ago), licensed Apache-2.0. It adds 82 tokens to every session and 4,142 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to git-wrapup, differing in 96 lines, and is treated as a copy.
Other skills, from other repositories
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled…
repository-manager-bulk-git-operations
Bulk, parallel git operations across a whole workspace of repositories via the repository-manager MCP server — clone, pull, push, add, commit, pre-commit, phased push, and enumerate every repo across a GitLab instance / GitHub org into an ingest manifest (which also natively ingests them into the knowledge graph as…
git-workflow
Git workflow patterns including branching strategies, commit conventions, merge vs rebase, atomic commits, worktrees, change summaries, and disciplined version control for AI agents and developer teams.
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). Verify, commit. Stops at "committed locally on main" — or, when the project releases through a release PR, at "release branch pushed, PR open". No tag, no push to…
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). Verify, commit. Stops at "committed locally on main" — or, when the project releases through a release PR, at "release branch pushed, PR open". No tag, no push to…
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled…