Borrowing it
Nothing to install: this file belongs to Edison-Watch/Custom-MCPs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Edison-Watch/Custom-MCPs/main/.agents/skills/push-release/SKILL.mdgit clone --depth 1 https://github.com/Edison-Watch/Custom-MCPsWrote 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/edison-watch/custom-mcps/push-release)<a href="https://agentmods.dev/skills/edison-watch/custom-mcps/push-release"><img src="https://agentmods.dev/badge/skills/edison-watch/custom-mcps/push-release/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/edison-watch/custom-mcps/push-release"><img src="https://agentmods.dev/badge/skills/edison-watch/custom-mcps/push-release.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.00062 | $0.01171 |
| Opus 5.5 | $0.00025 | $0.00468 |
| Sonnet 5.5 | $0.00012 | $0.00234 |
| Haiku 4.5 | $0.00006 | $0.00117 |
Grade A, and why
push-release 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Push Release
This project ships one wheel to PyPI containing all three console scripts (edisonmcps, edisonmcps-api, edisonmcps-mcp) at a single version. One tag push, one PyPI publish - there is no separate PyPI step for the API or MCP. Downstream users pip install the package and run whichever entry point they want; the API and MCP server aren't deployed by this repo. The MCP Registry entry refreshes automatically on the same tag (mcp-registry-publish.yml), so it's discovery metadata, not a second distribution.
Workflow
Execute these steps in order. Confirm with the user before running make bump_version and before pushing - tags are public and a published version cannot be unpublished from PyPI.
1. Pre-flight
Make sure main is clean and CI passes locally:
git status # working tree must be clean
git rev-parse --abbrev-ref HEAD # must be on main
make ci && make test
If anything fails, stop and report. Do not proceed with a broken main.
2. Pick the bump level
Ask the user which bump if not specified:
BUMP=patch(default) - bug fixes, no API change.0.1.1 -> 0.1.2BUMP=minor- additive features, backwards compatible.0.1.1 -> 0.2.0BUMP=major- breaking changes.0.1.1 -> 1.0.0
3. Bump the version
make bump_version BUMP=patch # or minor / major
This:
- updates
pyproject.tomlversion = "x.y.z" - creates a
Release vX.Y.Zcommit - creates an annotated tag
vX.Y.Z
The Makefile target refuses to run if the working tree or staging area is dirty.
4. Push with tags
git push origin main --follow-tags
The tag push is what triggers the release - without --follow-tags only the commit is pushed and nothing publishes.
5. Verify
Two GitHub Actions workflows fire on the v* tag:
- Release (
.github/workflows/release.yml)- Runs
make ciandmake test - Builds the package with
uv build - Publishes to PyPI via OIDC trusted publishing
- Creates a GitHub Release with auto-generated notes, wheel, and sdist
- Runs
- MCP Registry Publish (
.github/workflows/mcp-registry-publish.yml)- Authenticates via GitHub OIDC
- Publishes the MCP server to the MCP Registry
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 · 111 lines · 62 tokens per session scan A 94f7666b2048
push-release is a skill published in the GitHub repository Edison-Watch/Custom-MCPs (0 stars, last pushed 2d ago), licensed MIT. It adds 62 tokens to every session and 1,171 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release
Fully automate a release with version-bump and childhood.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.