Borrowing it
Nothing to install: this file belongs to paultyng/testagent. 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/paultyng/testagent/main/.claude/skills/publish-release/SKILL.mdgit clone --depth 1 https://github.com/paultyng/testagentWrote 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/paultyng/testagent/publish-release)<a href="https://agentmods.dev/skills/paultyng/testagent/publish-release"><img src="https://agentmods.dev/badge/skills/paultyng/testagent/publish-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/paultyng/testagent/publish-release"><img src="https://agentmods.dev/badge/skills/paultyng/testagent/publish-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.00050 | $0.01753 |
| Opus 5.5 | $0.00020 | $0.00701 |
| Sonnet 5.5 | $0.00010 | $0.00351 |
| Haiku 4.5 | $0.00005 | $0.00175 |
Grade A, and why
publish-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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
publish-release
Execute the release process documented in RELEASING.md. RELEASING.md is the policy source-of-record: semver scope, the bump table keyed to testagent's public surface, two runbooks, recovery branches. This skill is the executor: it cites RELEASING.md sections by anchor, performs each step, and gates on the one combined decision a human must own (version number + release-notes copy).
1. Preflight
git checkout main
git pull --ff-only
git status --porcelain # must be empty
task ci # full local build + lint + test
gh auth status # GH_TOKEN scope: repo
Identify the previous tag:
PREV=$(git describe --tags --abbrev=0)
If any preflight step fails, stop and report. Do not proceed — release should always cut from a clean, green main.
2. Surface diff + bump analysis
Run the surface-touching diff from RELEASING.md § Pre-tag checklist:
git log $PREV..HEAD --oneline
git diff $PREV..HEAD -- main.go cmd/ internal/slash/slash.go \
internal/hooks/hooks.go cmd/claude/print.go
Group commit subjects by Conventional Commits type (feat:,
fix:, refactor:, chore:, docs:, ci:, test:,
BREAKING CHANGE:). For each surface-touching change, map to the
bump table at RELEASING.md § Semver policy.
- Any
BREAKING CHANGE:footer or!in the subject → major (but see the v0.x clamp below). - New flag / slash command / hook event / public surface → minor.
- Pure bug fix / internal refactor / docs / test → patch.
v0.x clamp: until v1.0.0, the project's convention is to clamp
everything to patch unless the user explicitly overrides. New
features still go in, just packaged as v0.Y.Z+1 not v0.Y+1.0.
This trades semver-strictness for release cadence and is documented
in RELEASING.md.
Output: proposed bump (patch / minor / major) with file-and-
line evidence per category.
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 · 213 lines · 50 tokens per session scan A 12995bdaa213
publish-release is a skill published in the GitHub repository paultyng/testagent (7 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 1,753 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
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
pi-package-sandbox-test
Use when verifying that published Pi packages install and load for normal users, including pi.dev package compatibility checks, release validation, Daytona sandbox tests, and package installability audits.
versioning-by-impact
Use when completing a task and deciding whether repository changes require a semantic version bump and changelog entry before commit/push.
ship
Ship phase. Runs isolated integration test in a fresh worktree, creates a PR with full spec + audit report in the body, watches CI, and auto-fixes failures.
automating-devops
DevOps knowledge reference covering Git workflows, testing strategies, DevSecOps, release pipeline orchestration (release.yml, multi-arch images, cosign integration), CI/CD pipelines, database management, observability, and performance optimization. Use when working with Git, CI/CD, release pipelines, ghcr image…
release-candidate-preflight
Use when a release candidate or RC needs a go/no-go readiness decision across required artifacts, test summaries, known issues, approvals, compatibility, monitoring, and rollback.