Borrowing it
Nothing to install: this file belongs to AetherCore-Dev/ag402. 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/AetherCore-Dev/ag402/main/.claude/skills/releasing-to-pypi/SKILL.mdgit clone --depth 1 https://github.com/AetherCore-Dev/ag402Wrote 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/aethercore-dev/ag402/releasing-to-pypi)<a href="https://agentmods.dev/skills/aethercore-dev/ag402/releasing-to-pypi"><img src="https://agentmods.dev/badge/skills/aethercore-dev/ag402/releasing-to-pypi/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/aethercore-dev/ag402/releasing-to-pypi"><img src="https://agentmods.dev/badge/skills/aethercore-dev/ag402/releasing-to-pypi.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.00047 | $0.02374 |
| Opus 5 | $0.00023 | $0.01187 |
| Sonnet 5 | $0.00009 | $0.00475 |
| Haiku 4.5 | $0.00005 | $0.00237 |
Grade A, and why
releasing-to-pypi 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 9d 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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Releasing to PyPI
Overview
A release to PyPI in this project requires all steps completed atomically before pushing. The publish workflow triggers on GitHub Release creation and checks out the tag's commit — if that commit has wrong versions, stale lint, or missing changelog, the release fails and cannot be re-uploaded to PyPI (immutable filenames).
Core principle: The tag must point to a commit where every file is release-ready. Work backwards from that constraint.
When to Use
- Committing code that will be tagged for release
- Bumping versions for a new PyPI publish
- Creating any git tag prefixed with
v
The Checklist
MANDATORY: Execute every step in order. Do not skip. Do not reorder.
Step 1: Lint BEFORE Committing
ruff check protocol/ core/ adapters/
If lint fails, fix it. Never commit code that fails lint — fixing lint after commit requires either amend (breaks protected branches) or an extra commit (splits changes, tag placement becomes error-prone).
Step 2: Run ALL Tests BEFORE Committing
# Protocol tests
pytest protocol/tests/ --timeout=30
# Core tests (excluding on-chain)
pytest core/tests/ --timeout=30 -m "not devnet and not localnet and not mainnet"
# Adapter tests
cd adapters/mcp && pytest tests/ --timeout=30 && cd ../..
cd adapters/client_mcp && pytest tests/ --timeout=30 && cd ../..
All tests must pass. Do not commit with known failures.
Step 3: Version Bump — ALL 10 Files in ONE Commit
Determine the next version. Check existing tags:
git tag -l 'v*' --sort=-v:refname | head -5
Update all 10 files in a single commit:
| # | File | Field | Notes |
|---|---|---|---|
| 1 | protocol/pyproject.toml |
version = "X.Y.Z" |
|
| 2 | protocol/open402/__init__.py |
__version__ = "X.Y.Z" |
⚠️ Easy to forget |
| 3 | core/pyproject.toml |
version = "X.Y.Z" |
|
| 4 | core/ag402_core/__init__.py |
__version__ = "X.Y.Z" |
⚠️ Easy to forget |
| 5 | adapters/mcp/pyproject.toml |
version = "X.Y.Z" |
|
| 6 | adapters/mcp/ag402_mcp/__init__.py |
__version__ = "X.Y.Z" |
⚠️ Easy to forget |
| 7 | adapters/client_mcp/pyproject.toml |
version = "X.Y.Z" |
|
| 8 | adapters/client_mcp/ag402_client_mcp/__init__.py |
__version__ = "X.Y.Z" |
⚠️ Easy to forget |
| 9 | adapters/client_mcp/tests/test_server.py |
assert __version__ == "X.Y.Z" |
⚠️ Test will fail in CI if missed |
| 10 | CHANGELOG.md |
Add ## [X.Y.Z] section at top |
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.
- 9d ago First seen · 224 lines · 47 tokens per session scan A ec5ef7c73cde
releasing-to-pypi is a skill published in the GitHub repository AetherCore-Dev/ag402 (9 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 2,374 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
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.
Release Notes Generator
Generate professional software release notes from a commit log: classify changes, write user-facing summaries, draft a publishable announcement, and assess release readiness. Use for release, changelog, version, and deploy requests.
pinned-release-checklist
Minimal guidance-only Skill used by release-pinned compatibility examples.
Release Readiness Reviewer
Reviews a release candidate and produces a go/no-go readiness decision.
Release Checklist
Check release readiness and record a release note. Use for release and rollback requests.
python-packaging
Create distributable Python packages with proper project structure, setup.py/pyproject.toml, and publishing to PyPI. Use when packaging Python libraries, creating CLI tools, or distributing Python code.