Borrowing it
Nothing to install: this file belongs to milzamsz/flaredeck. 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/milzamsz/flaredeck/main/.agents/skills/flaredeck-release/SKILL.mdgit clone --depth 1 https://github.com/milzamsz/flaredeckWrote 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/milzamsz/flaredeck/flaredeck-release)<a href="https://agentmods.dev/skills/milzamsz/flaredeck/flaredeck-release"><img src="https://agentmods.dev/badge/skills/milzamsz/flaredeck/flaredeck-release.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.00049 | $0.00280 |
| Opus 5 | $0.00024 | $0.00140 |
| Sonnet 5 | $0.00010 | $0.00056 |
| Haiku 4.5 | $0.00005 | $0.00028 |
Grade A, and why
flaredeck-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 6d 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
FlareDeck Release
Preconditions
- implementation and verification tasks are complete;
- release scope and version are approved;
- signing configuration is available through secure CI or local release environment;
- no signing key rotation is planned inside the release task.
Procedure
- Read
RELEASING.md, current workflow, Phase 9 plan, and release checklist. - Confirm desktop, CLI, MCP, schema, and data-migration version compatibility.
- Run full verification and release builds on supported targets.
- Smoke-test existing profile migration, tunnel operation, CLI doctor, and MCP discovery.
- Verify artifact names, stable links, updater metadata, signatures, and checksums.
- Inspect artifacts and logs for secrets.
- Prepare release notes with migration and known limitations.
- Record rollback and unsupported downgrade boundaries.
Output
- artifact matrix;
- platform test matrix;
- migration results;
- signature/checksum results;
- release decision;
- release notes;
- known issues and rollback.
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.
- 6d ago First seen · 37 lines · 49 tokens per session scan A 7b1d1af4c1da
flaredeck-release is a skill published in the GitHub repository milzamsz/flaredeck (5 stars, last pushed 4d ago), licensed MIT. It adds 49 tokens to every session and 280 once invoked, about $0.0002 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
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.