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 ksmaster03/claude-canfly-skill --skill release-deploygit clone --depth 1 https://github.com/ksmaster03/claude-canfly-skillWrote 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/ksmaster03/claude-canfly-skill/release-deploy)<a href="https://agentmods.dev/skills/ksmaster03/claude-canfly-skill/release-deploy"><img src="https://agentmods.dev/badge/skills/ksmaster03/claude-canfly-skill/release-deploy.svg" alt="Measured on agentmods" 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.00124 | $0.03473 |
| Opus 5 | $0.00062 | $0.01736 |
| Sonnet 5 | $0.00025 | $0.00695 |
| Haiku 4.5 | $0.00012 | $0.00347 |
Grade A, and why
release-deploy 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 7d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 7d ago First seen · 156 lines · 124 tokens per session scan A 7d1dc104ecb7
release-deploy is a skill published in the GitHub repository ksmaster03/claude-canfly-skill (11 stars, last pushed 24d ago), with no licence file. It adds 124 tokens to every session and 3,473 once invoked, about $0.0006 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-30.
Other skills, from other repositories
release-versioning
Discipline for release classification, version bumps, and changelogs, Conventional Commits classify the release range, SemVer computes the version from those commits, Keep a Changelog renders the result. Use when the user asks to cut a release, bump a version, write a changelog, decide if a change is a…
ship-task
Use to wrap up a finished task - set status to done, merge, clean up.
safe-deployment
Discipline for shipping changes reversibly, decouple deploy (code reaches production) from release (users see it) with feature flags, roll out progressively, and define the automated rollback trigger before shipping, not during the incident. Use when the user asks how to deploy a risky change, choose between…
06-release
Ship the verified sprint: the release gate the spine protects, then a verified deploy. Release ≠ runnable — the slice is runnable from /04's handoff §(e) onward; this seat adds deploy + verification, not runnability. GATE FIRST: BLOCKs on a non-SHIP qa-report (unless the director ruled every High in §(h), dated), an…
checkpoint
Save a checkpoint — bump version, commit, push. Use when work is complete and ready to ship without the full finish protocol.
bump
Bumping project version and updating changelog atomically. Use when releasing a new version — patch, minor, or major.