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 agentmods add skills/gpauloski/python-template/releasenpx skills add gpauloski/python-template --skill releasegit clone --depth 1 https://github.com/gpauloski/python-templateWhat 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 | $0.00047 | $0.00337 |
| Opus 5 | $0.00023 | $0.00169 |
| Sonnet 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 yesterday.
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.
- yesterday 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 7d ago), licensed MIT. It adds 47 tokens to every session and 337 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-30.
Other skills, from other repositories
django-celery-expert
Expert Django Celery guidance for asynchronous task processing. Use when designing background tasks, configuring Celery workers, handling task retries and errors, optimizing Celery performance, implementing periodic tasks with Celery Beat, or setting up production monitoring for Celery. Do not use for general Django…
django-expert
Expert Django backend development guidance. Use when creating Django models, views, serializers, or APIs; debugging ORM queries or migrations; optimizing database performance; implementing authentication; writing tests; or working with Django REST Framework. Follows Django best practices and modern patterns.
heaven-style
Standalone personal code-quality, architecture, documentation, graphical-interface, and project-management guide for TypeScript and Python repositories. Use when writing or reviewing code or docs, designing architecture or UI, refactoring, or aligning tests; apply repository policy first, then shared design philosophy…
add-vertical
Use this skill when adding a new feature vertical to this template — a domain aggregate with its port, repository, application service, DTOs, endpoint, and tests. Trigger it for requests like "add an endpoint", "add a new entity", "build the X feature", or "wire up a new service".
aget-close-project
Close a PROJECTPLAN with verifiable-assertion gate (V-tests + commits + retrospective), deferred-surface scan for next-plan handoff, and status transition (ACTIVE → COMPLETE / CLOSED / ABANDONED / SUPERSEDED). Strict counterpart to /aget-create-project (D71 Layer 2). Closes asymmetric verb-pair gap at PROJECTPLAN…
aget-release-critique
Adversarial review with the Critic perspective of the Release Delivery Triad (L818). Dual-mandate: spec coverage audit + deep bug finding.