Borrowing it
Nothing to install: this file belongs to osama-raddad/FireCrasher. 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/osama-raddad/FireCrasher/master/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/osama-raddad/FireCrasherWrote 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/osama-raddad/firecrasher/release)<a href="https://agentmods.dev/skills/osama-raddad/firecrasher/release"><img src="https://agentmods.dev/badge/skills/osama-raddad/firecrasher/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.00056 | $0.00705 |
| Opus 5 | $0.00028 | $0.00352 |
| Sonnet 5 | $0.00011 | $0.00141 |
| Haiku 4.5 | $0.00006 | $0.00071 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release FireCrasher
FireCrasher is distributed through JitPack, which builds from a git tag —
there is no separate publish pipeline in this repo. A release is: get the
version and metadata in sync, verify, commit, and tag. JitPack does the rest
(jitpack.yml pins JDK 21; coordinates are remapped to
com.github.osama-raddad:FireCrasher:<tag>).
The current version is 3.0.0. Pick the new version with semantic versioning:
a breaking public API change (anything that alters firecrasher/api/firecrasher.api
incompatibly) is a major bump.
Steps
-
Land the code first. All feature/fix work for the release should already be merged or staged. Run the
run-checksskill and confirm green. -
Bump
VERSION_NAMEinfirecrasher/build.gradle(theversion = project.findProperty('VERSION_NAME') ?: '3.0.0'fallback in thepublishingblock). Set it to the new version. -
Update
README.md:- The install snippet:
implementation 'com.github.osama-raddad:FireCrasher:<new>'. - Add a "What's new in " section describing the changes (breaking changes first, and call out any minSdk/toolchain change).
- The install snippet:
-
Sync the ABI baseline. If the public API changed, run the
update-abi-baselineskill sofirecrasher/api/firecrasher.apimatches.apiCheckmust pass. -
Verify the whole thing once more:
./gradlew build --stacktrace -
Commit the version bump, README, and any baseline change together, e.g.
Release 2.2.0. -
Tag and push (the tag is what JitPack builds):
git tag <new> # e.g. git tag 2.2.0 — match the README's coordinate git push origin <new>Tag names become the JitPack version verbatim, so the tag must equal the version string in the README install snippet.
-
Confirm the JitPack build at
https://jitpack.io/#osama-raddad/FireCrasherresolves the new version (first fetch triggers the build).
Notes
- The demo
app/module has its ownversionCode/versionName; it is not published and does not need to track the library version. - Never edit
firecrasher.apiby hand to force a release — regenerate it withapiDump. - Don't push tags to a feature branch's flow; releases are cut from the release-ready commit on the mainline per the repo's branching rules.
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 · 63 lines · 56 tokens per session scan A df9fcde57020
release is a skill published in the GitHub repository osama-raddad/FireCrasher (148 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 56 tokens to every session and 705 once invoked, about $0.0003 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
changelog-writer
Write external-facing changelog and release note entries in a pithy, tastefully sassy, occasionally clever voice that makes software updates fun to read without burying what actually shipped. Use this skill whenever someone asks to write, draft, or review a changelog entry, release notes, "what's new" post, or product…
release-process
Step-by-step release checklist for Squad — prevents v0.8.22-style disasters.
npm-publish
Publish the create-cmp CLI to npm as the create-cmp-cli package. Use this when the user asks to "publish create-cmp to npm", "release a new version", "ship create-cmp-cli", "npm publish this", "cut a release", or wants npx create-cmp-cli to work. Runs unattended when a granular npm token is installed in the user's…
github-actions-multiplatform-release
Structure a GitHub Actions release pipeline for a multiplatform desktop app so one Linux runner cross-builds every platform's artifacts and a second, tiny macOS job does only the one step that genuinely requires macOS — with artifact handoff between them and no compilation on the costly runner; reach for it when your…
git-pr-strategy
Apply safe branching, commits, conflict resolution, review ownership, merge, rollback, and release-tag rules.
build-release-engineer
!cat skills/shared/game-visual-foundations.md 2>/dev/null || echo "=== Visual Foundations not loaded ===" !cat skills/shared/protocols/ux-protocol.md 2>/dev/null || true !cat skills/shared/protocols/input-validation.md 2>/dev/null || true !cat skills/shared/protocols/tool-efficiency.md 2>/dev/null || true !cat…