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/mcp-reporter --skill git-wrapupgit clone --depth 1 https://github.com/cyanheads/mcp-reporterWrote 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/mcp-reporter/git-wrapup)<a href="https://agentmods.dev/skills/cyanheads/mcp-reporter/git-wrapup"><img src="https://agentmods.dev/badge/skills/cyanheads/mcp-reporter/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/mcp-reporter/git-wrapup"><img src="https://agentmods.dev/badge/skills/cyanheads/mcp-reporter/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.00033 | $0.01104 |
| Opus 5.5 | $0.00013 | $0.00442 |
| Sonnet 5.5 | $0.00007 | $0.00221 |
| Haiku 4.5 | $0.00003 | $0.00110 |
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 1mo 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git wrapup
Run only with explicit commit/wrapup authorization. Read CLAUDE.md and the full diff first. This workflow stops at a local commit/tag; publishing belongs to release-and-publish.
1. Review the work
Read status, diff, recent history and the last tag. Include complete pre-existing changes when authorized, but do not overwrite or sweep another active writer's work. Never stash or use a worktree. If nothing changed, stop.
Confirm every reported fix exists, tests cover it, and relevant GitHub issues have current bodies. Review code, tests, docs, package files and generated output together. Do not publish reports from private server configurations.
2. Establish the version
Read package.json and use the user's release instruction. Apply semver to this CLI and library: patches fix compatible behavior, minors add compatible functionality, majors cover incompatible public APIs, module formats or runtime floors. Honor the release line in CLAUDE.md; do not promote this package to 2.x without user authorization. Within an authorized line, document consumer-incompatible changes with breaking frontmatter and upgrade instructions. Surface a genuinely undecided version before creating release artifacts. The SDK version is not this package's version.
3. Synchronize identity
Update package.json, the Bun lockfile and README version badge together. src/version.ts reads package metadata for both executable entry points and the MCP handshake; do not introduce another version literal. Check all current docs for stale versions; leave historical changelogs unchanged. Keep the npm name unscoped as mcp-reporter.
4. Write the changelog
Use changelog/template.md to create changelog/<major.minor>.x/<version>.md with # <version> — YYYY-MM-DD. No Unreleased header.
Required frontmatter: a quoted one-line summary of at most 350 characters, breaking, and security. Write the summary last from the body. Security is true for fixes in this package's source, not dependency-only advisories. Optional agent-notes contain upgrade actions only.
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.
- 1mo ago First seen · 74 lines · 33 tokens per session scan A 0f605294132d
git-wrapup is a skill published in the GitHub repository cyanheads/mcp-reporter (12 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 1,104 once invoked, about $0.0001 per session on Opus 5.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-09.
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). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…
kirocrew-prepare-pr
LOAD THIS FOR EVERY KIRO CREW PR you open or update (Kiro Crew repo only; not other repos or CRs). Runs the whole loop — issue + tier, commit, sync, squash, push, drive CI and AI review to green, fix a red main, arm auto-merge and watch it land (24h). 'push my changes' = prepare-only.
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.
yeet
Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (gh).
ship-change
Ship an OpenSpec change after openspec-apply completes. When only QA/manual tasks remain, marks them done (tested later), archives + syncs specs, commits, pushes, opens a PR against develop, watches CI, waits for CodeRabbit, auto-applies safe fixes and re-pushes, loops until CI green + no actionable review threads…
chinese-commit-conventions
A Chinese-language reference for writing commit messages and changelogs, which record code changes and releases.