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 gpauloski/python-template --skill releasegit clone --depth 1 https://github.com/gpauloski/python-templateWrote 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/gpauloski/python-template/release)<a href="https://agentmods.dev/skills/gpauloski/python-template/release"><img src="https://agentmods.dev/badge/skills/gpauloski/python-template/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/gpauloski/python-template/release"><img src="https://agentmods.dev/badge/skills/gpauloski/python-template/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00337 |
| Opus 5.5 | $0.00019 | $0.00135 |
| Sonnet 5.5 | $0.00009 | $0.00067 |
| Haiku 4.5 | $0.00005 | $0.00034 |
Grade A, and why
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.
What it actually says
Cut a release
Versioning is derived from git tags via setuptools_scm, and publishing is
automated by .github/workflows/publish.yml. See
docs/contributing/releases.md for the authoritative process.
- Confirm
mainis green (CI passing) and decide the version{VERSION}(semvermajor.minor.patch, optional PEP 440 pre/post/dev suffix). - Create and push an annotated, signed tag prefixed with
v:git tag -s v{VERSION} -m "pypkg v{VERSION}" git push origin v{VERSION} - Create a GitHub Release from the tag titled
pypkg v{VERSION}:- Official release: use "Generate release notes", set the previous official tag as the baseline, add an "Upgrade Steps" section, verify PR labels sort the notes correctly, and mark it "latest".
- Pre-release: skip generated notes and mark it "pre-release".
- Publishing the release triggers the
publishworkflow, which builds withuv build, uploads to PyPI via Trusted Publishing, and deploys versioned docs withmike. Confirm both the PyPI upload and the docs deploy succeeded.
Do not push tags or create releases without explicit confirmation from the user.
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 · 29 lines · 47 tokens per session scan A a4ec4bc9eb4f
release is a skill published in the GitHub repository gpauloski/python-template (19 stars, last pushed 4d ago), licensed MIT. It adds 47 tokens to every session and 337 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-30.
Other skills, from other repositories
aget-release-build
Execute release gate deliverables with the Builder perspective of the Release Delivery Triad (L818) — speed-optimized execution asking whether the work is done, fast, and functional. Superseded by /aget-create-release.
aget-promote-issue
Promote issues from the private tracker (gmelli/aget-aget) to the public tracker (aget-framework/aget) through governed content sanitization and principal approval, preventing private information leakage at the promotion boundary (L638, R-ISSUE-011).
aget-record-lesson
Record lessons learned from sessions as persistent, searchable, committable artifacts. Classifies each lesson as Framework (help other AGETs) or Domain (help principal).
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
merge-seed
Merge upstream React Starter Kit updates (the seed remote) into main, preserving this project's identity, scope, and behavior. Use when asked to sync, pull, or merge the seed / starter kit / upstream template.
cli-release
Release and recover first-party Composio CLI binaries through Build CLI Binaries, including automatic beta builds, promote-stable dispatches, beta-tag selection, asset and installation verification, and failed release recovery. Use when a contributor asks to build a CLI beta, publish or promote a stable CLI version…