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 release-and-publishgit 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/release-and-publish)<a href="https://agentmods.dev/skills/cyanheads/mcp-reporter/release-and-publish"><img src="https://agentmods.dev/badge/skills/cyanheads/mcp-reporter/release-and-publish/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/release-and-publish"><img src="https://agentmods.dev/badge/skills/cyanheads/mcp-reporter/release-and-publish.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.00026 | $0.00665 |
| Opus 5 | $0.00013 | $0.00332 |
| Sonnet 5 | $0.00005 | $0.00133 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
release-and-publish 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release and publish
Requires explicit publishing authorization and a completed git-wrapup: synchronized version/changelog, reviewed commits, annotated v<version> at HEAD, and no unresolved working-tree changes. Read CLAUDE.md. This CLI targets npm and GitHub Releases; no MCP Registry, MCPB, Docker, or hosting steps apply.
1. Verify wrapup
Read package version, current branch, origin, tag target, annotation and status. Verify tag signing when configured; a signature block must never be interpreted as release text. An existing tag conflict is a stop, not permission to replace it.
2. Run the gates
Run bun run devcheck, bun run rebuild, bun run test:package, and bun audit. Inspect output and resolve failures/warnings. Confirm the package allowlist excludes local configs, reports, tests, backups and credentials. Review any transitive advisory by its actual installed dependency path.
3. Push the reviewed commits and exact tag
Push the intended branch, then the exact release tag. Do not push unrelated tags. A rejection requires reconciliation, never force-push or stash. A PR route does not authorize merging.
4. Publish npm
Run bun publish --access public. Verify the name is still mcp-reporter. Complete configured interactive authentication when requested by the registry. An already-published version is successful only after querying and verifying that exact package/version; never treat arbitrary publish errors as success.
5. Record skipped server destinations
There is no server.json, MCP Registry registration, MCPB bundle or container deployment for this client. Do not create placeholder metadata or destinations to satisfy a server workflow.
6. Create the GitHub Release
Run bun run release:github. It uses the annotated tag and creates the title v<VERSION>: <tag subject> with --verify-tag --notes-from-tag. The annotation's subject omits the version and its flat digest ends in a per-version changelog link. Existing-release recovery updates the title; inspect the existing body before replacing any published content.
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 · 49 lines · 26 tokens per session scan A 904f7595e6b4
release-and-publish is a skill published in the GitHub repository cyanheads/mcp-reporter (12 stars, last pushed 3d ago), licensed Apache-2.0. It adds 26 tokens to every session and 665 once invoked, about $0.0001 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-09.
Other skills, from other repositories
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.
update-set-workflow
Manage ServiceNow update sets — create named sets before any development, ensure autoswitch tracks API changes under the OAuth service account, complete on done, and export for promotion. Mandatory for all change-producing work.
pypi-release
This skill should be used when releasing tunacode-cli to PyPI. It keeps the existing local release checks, then hands the actual PyPI upload to a GitHub Actions workflow that uses the repository's PYPIAPITOKEN secret.
github
Use the gh CLI for GitHub issues, PR status, CI/logs, comments, reviews, releases, and API queries.
changelog
Update CHANGELOG.md with user-facing changes. Use when the user wants to update the changelog, prepare for a release, or document what changed since the last version.
openhandoff-release
Prepare a tested, documented, and reproducible OpenHandoff release without publishing or tagging until the user approves.