Borrowing it
Nothing to install: this file belongs to CynaCons/powerplan. 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/CynaCons/powerplan/main/.grok/skills/release-powerplan/SKILL.mdgit clone --depth 1 https://github.com/CynaCons/powerplanWrote 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/cynacons/powerplan/release-powerplan)<a href="https://agentmods.dev/skills/cynacons/powerplan/release-powerplan"><img src="https://agentmods.dev/badge/skills/cynacons/powerplan/release-powerplan/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/cynacons/powerplan/release-powerplan"><img src="https://agentmods.dev/badge/skills/cynacons/powerplan/release-powerplan.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.00091 | $0.00523 |
| Opus 5.5 | $0.00036 | $0.00209 |
| Sonnet 5.5 | $0.00018 | $0.00105 |
| Haiku 4.5 | $0.00009 | $0.00052 |
Grade A, and why
release-powerplan 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 powerplan
Before any version bump or tag, read docs/RELEASING.md. That file owns names, URLs, workflow filenames, and failure history. Do not copy those tables into this skill.
Do
- Confirm the product change is on
mainandpython -m pytest -qis green. - Bump the version in every file listed under Version files in
docs/RELEASING.md. - Commit,
git push origin main, tagvX.Y.Z, push the tag,gh release create. - Make sure Publish is running —
gh run list --workflow=Publish --limit 2first. If the tag push already queued a run forvX.Y.Z, watch it and do not dispatch (a second run fails at the registry withduplicate version). If nothing queued (agent pushes with an App token do not trigger workflows):gh workflow run Publish --ref vX.Y.Z, thengh run watch <id> --exit-status. Ifsite/**changed, alsogh workflow run "Deploy Landing Page". - Verify PyPI and the MCP Registry URLs in
docs/RELEASING.md. - Record progress with powerplan tools (
complete_task/close_iteration). Do not hand-editPLAN.md.
Constraints
- PyPI project is
powerplan-mcp. MCP server name and import staypowerplan. - Registry name is
io.github.CynaCons/powerplan(GitHub org casing). - Publish channel is PyPI + MCP Registry. Not npm.
- Never retag a version that already has a wheel on PyPI.
- Never remove
mcp-name: io.github.CynaCons/powerplanfromREADME.md. - Site (
site/) deploys separately; a tag is not a Pages deploy.
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 Changed · +2 lines b42d4651d616
- 2mo ago First seen · 39 lines · 91 tokens per session scan A 312022559fce
release-powerplan is a skill published in the GitHub repository CynaCons/powerplan (0 stars, last pushed 2d ago), licensed MIT. It adds 91 tokens to every session and 523 once invoked, about $0.0004 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
repository-manager-bulk-git-operations
Bulk, parallel git operations across a whole workspace of repositories via the repository-manager MCP server — clone, pull, push, add, commit, pre-commit, and enumerate every repo across a GitLab instance / GitHub org into an ingest manifest (which also natively ingests them into the knowledge graph as typed…
repository-manager-workspace-release
Roll a dependency floor across the fleet deterministically and manage the workspace.yml manifest — via rmrollout (or repository-manager rollout) and rmworkspace. A rollout selects the workspace.yml group's non-archived repos that depend on the package, plans per repo from main into a resumable ledger, applies each…
metagit-release-audit
Mandatory before calling work complete when the session changed repo files. Runs format, lint, tests, integration tests, context-aware pip-audit/bandit, and optional gitleaks via task qa:prepush. Use before push, release, or hand-off.
unity-release-readiness
Use before shipping a Unity build: version, build scenes, broken refs, assembly cycles, large assets, changelog, and package health.
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
orchard-release
Check deployment evidence and recovery conditions.