Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Gentleman-Programming/gentle-pinpx agentmods add skills/gentleman-programming/gentle-pi/releaseWrote 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/gentleman-programming/gentle-pi/release)<a href="https://agentmods.dev/skills/gentleman-programming/gentle-pi/release"><img src="https://agentmods.dev/badge/skills/gentleman-programming/gentle-pi/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/gentleman-programming/gentle-pi/release"><img src="https://agentmods.dev/badge/skills/gentleman-programming/gentle-pi/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.00028 | $0.01247 |
| Opus 5.5 | $0.00011 | $0.00499 |
| Sonnet 5.5 | $0.00006 | $0.00249 |
| Haiku 4.5 | $0.00003 | $0.00125 |
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.
How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
Use this skill when preparing, publishing, or verifying a gentle-pi release.
Hard Rules
- Do not publish
gentle-pito npm from a local machine. - npm publishing MUST go through the GitHub Actions workflow
.github/workflows/publish.ymlso provenance, environment protection, and registry credentials are controlled by GitHub. - Dispatch the trusted workflow definition from protected default
main, never from a release tag. Its only caller input is the exact annotated version tag. - Use a clean worktree for release commits. Do not package unrelated local files or scratch artifacts.
- Review outcomes are informational. Release delivery follows ordinary repository policy and must not be blocked, authorized, or rewritten by RDD.
- Never infer the release tag target from local
HEAD; use the freshly fetchedorigin/maincommit and the repository's normal release safeguards. - Never skip package verification. The publish workflow runs verification again, but local validation should still pass before tagging.
Release Procedure
-
Inspect state
git status --short git fetch origin main --tags git log --oneline --decorate --max-count=5 origin/main -
Prepare the release commit
- Apply only intended changes.
- Bump
package.jsonto the next semver version. - Keep lockfile changes out unless dependency resolution actually changed.
-
Verify locally
pnpm test node scripts/verify-package-files.mjs npm pack --dry-runnpm pack --dry-runverifies package contents and lifecycle scripts without entering a publish path. -
Commit and push
git add <intended-files> git commit -m "<type(scope): release-ready change>" git push origin HEAD:main git fetch origin main --tags -
Create and verify the exact version tag
version="$(node -p "require('./package.json').version")" tag="v${version}" release_sha="$(git rev-parse 'origin/main^{commit}')" test "$(git rev-parse 'HEAD^{commit}')" = "${release_sha}" test -z "$(git ls-remote --tags origin "refs/tags/${tag}")" git tag -a "${tag}" "${release_sha}" -m "gentle-pi ${tag}" test "$(git rev-parse "${tag}^{commit}")" = "${release_sha}" git fetch origin main test "$(git rev-parse 'origin/main^{commit}')" = "${release_sha}" git push origin "refs/tags/${tag}" git fetch --no-tags origin "refs/tags/${tag}" test "$(git rev-parse 'FETCH_HEAD^{commit}')" = "${release_sha}" gh release create "${tag}" \ --repo Gentleman-Programming/gentle-pi \ --verify-tag \ --title "gentle-pi ${tag}" \ --notes "<release notes>"
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 · 138 lines · 28 tokens per session scan A 4c6d45928368
release is a skill published in the GitHub repository Gentleman-Programming/gentle-pi (804 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 1,247 once invoked, about $0.0001 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
explain-pr
Explain a PR: the background problem and the proposed solution.
ship
Use when code is ready to ship — creates PRs, merges, deploys, and verifies. Handles the full PR-to-production pipeline. Triggers on /ship.
release-readiness
Use after review/qa/security/license-audit/privacy-check to compose a release decision before /ship. Returns OK only when all required upstream evidence is present and clean. Triggers on /release-readiness.
pi-sync
Daily upstream-sync job for the pi Go port — fetch upstream pi, triage every change since the recorded pin, port what's in scope, verify idiomatic + parity via independent reviews, update the ledger, and push. Use for "sync with upstream", "porting job", or as the scheduled daily run.
releasing-code
Prepare, publish, or repair a software release and write its release notes. Use for cutting a versioned release or editing release notes. NOT for updating an installed package, publishing articles, or discussing a release; for general documentation use documenting-code.
upload
Pre-upload gate for track handoff. Verifies review status, HLD approvals, deploy checklist, and validator chain before git upload or PR submission.