Borrowing it
Nothing to install: this file belongs to Fioooooooo/FylloCode. 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/Fioooooooo/FylloCode/main/.agents/skills/prepare-release/SKILL.mdgit clone --depth 1 https://github.com/Fioooooooo/FylloCodeWrote 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/fioooooooo/fyllocode/prepare-release)<a href="https://agentmods.dev/skills/fioooooooo/fyllocode/prepare-release"><img src="https://agentmods.dev/badge/skills/fioooooooo/fyllocode/prepare-release/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/fioooooooo/fyllocode/prepare-release"><img src="https://agentmods.dev/badge/skills/fioooooooo/fyllocode/prepare-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 31 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00087 | $0.02050 |
| Opus 5.5 | $0.00035 | $0.00820 |
| Sonnet 5.5 | $0.00017 | $0.00410 |
| Haiku 4.5 | $0.00009 | $0.00205 |
Grade A, and why
prepare-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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prepare Release
Prepare one evidence-backed release without losing documentation updates or bypassing repository safeguards. Support both the full workflow and focused changelog, documentation-audit, or release-note requests.
Read Before Acting
- Read the repository
AGENTS.md, relevantopenspec/specs/**, and applicableguidelines/**before editing. - Read documentation-audit.md for every full release or documentation audit.
- Read documentation-architecture-and-style.md in full before creating, restructuring, or rewriting product documentation.
- Read versioning.md before selecting or changing any application or bundled MCP server version.
- Read changelog.md before editing either root changelog.
- Read release-notes.md before drafting or publishing release notes.
- Read natural-writing.md before authoring or substantially rewriting any release-related prose.
- Inspect
git status --shortand preserve unrelated user changes. Never clean, reset, overwrite, or reformat unrelated work.
Establish the Release Boundary
Determine and report:
- user-provided target application version and release date;
- previous release tag and exact
previous_tag..HEADrange; - whether the release is stable or prerelease;
- requested stopping point: artifacts only, release commit, tag, push, or publication;
- bundled MCP server versions derived from their independent change boundaries, with evidence and rationale.
Use the latest relevant semantic-version tag as the default base. Require the user to provide the exact target application version, including any prerelease identifier; never infer the application version from commits, change size, or release contents. If it is missing, ask one concise question for it and stop until answered. Derive bundled MCP server versions yourself by following versioning.md; do not ask the user to choose those versions when the change boundary can be established from repository evidence.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 155 lines · 87 tokens per session scan A 4e54ebb3d4e8
prepare-release is a skill published in the GitHub repository Fioooooooo/FylloCode (28 stars, last pushed 1mo ago), licensed MIT. It adds 87 tokens to every session and 2,050 once invoked, about $0.0003 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-30.
prepare-release compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| prepare-releaseFioooooooo/FylloCode | Skill | 28 | 1mo ago | MIT | A | 87 | Codex |
| update-v8-versionopeninterpreter/openinterpreter | Skill | 69k | 3d ago | Apache-2.0 | A | 86 | Codex |
| updateme2resh/apexyard | Skill | 542 | yesterday | MIT | A | 27 | Claude Code |
| releaseme2resh/apexyard | Skill | 542 | yesterday | MIT | A | 33 | Claude Code |
| release-syncme2resh/apexyard | Skill | 542 | yesterday | MIT | A | 35 | Claude Code |
| babysit-propeninterpreter/openinterpreter | Skill | 69k | 3d ago | Apache-2.0 | A | 114 | Codex |
| codex-pr-bodyopeninterpreter/openinterpreter | Skill | 69k | 3d ago | Apache-2.0 | A | 17 | Codex |