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.
git 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/rules/guorunjie/skillpack-forge/release-ops-demo)<a href="https://agentmods.dev/rules/guorunjie/skillpack-forge/release-ops-demo"><img src="https://agentmods.dev/badge/rules/guorunjie/skillpack-forge/release-ops-demo/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/rules/guorunjie/skillpack-forge/release-ops-demo"><img src="https://agentmods.dev/badge/rules/guorunjie/skillpack-forge/release-ops-demo.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.00138 | $0.00138 |
| Opus 5.5 | $0.00055 | $0.00055 |
| Sonnet 5.5 | $0.00028 | $0.00028 |
| Haiku 4.5 | $0.00014 | $0.00014 |
Grade A, and why
release-ops-demo 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
release-ops-demo
Generated from skillpack.yaml by Skillpack Forge.
Release automation workflows for changelogs, tags, packages, and CI checks.
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
Commands
- install:
npm install - test:
npm test - build:
npm run build - release:
npm run release - check:
npm run check
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 · 25 lines · 138 tokens per session scan A 7c25f5ba903a
release-ops-demo is a cursor rule published in the GitHub repository guorunjie/skillpack-forge (1 stars, last pushed 4mo ago), licensed MIT. It adds 138 tokens to every session, about $0.0006 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 cursor rules, from other repositories
github
GitHub repository operations: PRs, issues, releases, branch protection, CODEOWNERS, Dependabot, and repo settings audits. Use when user says 'review my PR', 'create a release', 'cut a release', 'tag a release', 'set up branch protection', 'add CODEOWNERS', 'audit repo settings', 'is Dependabot configured', or asks…
github-cli
Apply when using the gh CLI to manage pull requests, issues, releases, or CI workflows on GitHub.
releasing-operator
when the user is releasing a new version of the Kubernetes operator.
release-manager
Release Orchestration & Versioning Specialist. Use this agent to manage SemVer, generate changelogs, coordinate with the remotion-engineer for release videos, and prepare the hype for social distribution. It ensures every deployment is a moment.
ci-cd-workflows
This rule provides guidance on the CI/CD pipeline, GitHub Actions workflows (defined in .github/workflows/), custom actions (in .github/actions/), versioning strategies, and release processes. Use this rule if the query involves CI/CD, build/test issues, release procedures, versioning questions, or if it references…
release
Git tag, CHANGELOG heading, package.json, and npm publish must share one semver. Use when releasing, shipping, deploying, tagging, or publishing npm.