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 guorunjie/skillpack-forge --skill release-ops-demo-release-automationgit clone --depth 1 https://github.com/guorunjie/skillpack-forgeWrote 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/guorunjie/skillpack-forge/release-ops-demo-release-automation)<a href="https://agentmods.dev/skills/guorunjie/skillpack-forge/release-ops-demo-release-automation"><img src="https://agentmods.dev/badge/skills/guorunjie/skillpack-forge/release-ops-demo-release-automation/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/guorunjie/skillpack-forge/release-ops-demo-release-automation"><img src="https://agentmods.dev/badge/skills/guorunjie/skillpack-forge/release-ops-demo-release-automation.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.00020 | $0.00194 |
| Opus 5 | $0.00010 | $0.00097 |
| Sonnet 5 | $0.00004 | $0.00039 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
release-ops-demo-release-automation 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 11d 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
release-ops-demo-release-automation
Generated from skillpack.yaml by Skillpack Forge.
Project
Release automation workflows for changelogs, tags, packages, and CI checks.
Workflow
- Inspect git status, recent commits, package metadata, and release history
- Run tests and package dry-run checks
- Prepare release notes from concrete changes
- Publish only after verifying the target registry or GitHub release state
Commands
- install:
npm install - test:
npm test - build:
npm run build - release:
npm run release - check:
npm run check
Principles
- Verify a clean worktree and passing checks before release steps
- Keep version, tag, package, and release notes aligned
- Treat publish credentials and tokens as sensitive
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.
- 11d ago First seen · 30 lines · 20 tokens per session scan A 5c945e50d0ca
release-ops-demo-release-automation is a skill published in the GitHub repository guorunjie/skillpack-forge (1 stars, last pushed 3mo ago), licensed MIT. It adds 20 tokens to every session and 194 once invoked, about $0.0001 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
trusted-publish
Publish a package from a git repo to its registry via OIDC Trusted Publishing — no long-lived tokens. Writes the GitHub Actions publish workflow, walks the user through the registry-side trust entry, releases, and verifies. Use when the user wants to publish or release a package to PyPI, npm, crates.io, or another…
github-cli
Apply when using the gh CLI to manage pull requests, issues, releases, or CI workflows on GitHub.
skill-release-management
Release planning and scheduling, semantic versioning (semver), rollout strategies (canary, blue-green, gradual), changelog generation, rollback procedures, production validation. Use when planning releases, creating rollout strategies, or managing version bumps.
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
release-skills
A release workflow for preparing and publishing a new version of a software project. A release is a named version that may include updated version files, release notes, tags, or a GitHub Release.
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.