FireCrasher: Skill for Claude Code

.claude/skills/release/SKILL.md

release is a skill for Claude Code from osama-raddad/FireCrasher. It costs 56 tokens per session (705 once invoked), scanned A, original, Apache-2.0.

A release procedure for the FireCrasher library, a reusable software package, distributed through JitPack, a service that builds packages from Git tags. It synchronizes the version, README, public API record, checks, commit, and release tag.

In plain words
What is it for?
Use it when publishing a new FireCrasher version, changing its version number, updating release notes or installation instructions, or handling public API changes.
Why use it?
It reduces the chance that the published version, installation instructions, documentation, and public API record disagree. It also checks the project before making the tag used for distribution.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is osama-raddad/FireCrasher's own configuration. It tells Claude Code how to work on FireCrasher itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything FireCrasher configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/osama-raddad/FireCrasher/master/.claude/skills/release/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/osama-raddad/FireCrasher

Made for: Claude Code.

Wrote 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.

agentmods badge for release

README.md
[![agentmods](https://agentmods.dev/badge/skills/osama-raddad/firecrasher/release.svg)](https://agentmods.dev/skills/osama-raddad/firecrasher/release)
Your own site
<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>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 705 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 7d ago against content hash df9fcde57020, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

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.

.claude/skills/release/SKILL.md · 63 lines

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

  1. Land the code first. All feature/fix work for the release should already be merged or staged. Run the run-checks skill and confirm green.

  2. Bump VERSION_NAME in firecrasher/build.gradle (the version = project.findProperty('VERSION_NAME') ?: '3.0.0' fallback in the publishing block). Set it to the new version.

  3. 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).
  4. Sync the ABI baseline. If the public API changed, run the update-abi-baseline skill so firecrasher/api/firecrasher.api matches. apiCheck must pass.

  5. Verify the whole thing once more:

    ./gradlew build --stacktrace
    
  6. Commit the version bump, README, and any baseline change together, e.g. Release 2.2.0.

  7. 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.

  8. Confirm the JitPack build at https://jitpack.io/#osama-raddad/FireCrasher resolves the new version (first fetch triggers the build).

Notes

  • The demo app/ module has its own versionCode/versionName; it is not published and does not need to track the library version.
  • Never edit firecrasher.api by hand to force a release — regenerate it with apiDump.
  • 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.

Read the full file on GitHub · 63 lines

Changes

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.

  1. 7d ago First seen · 63 lines · 56 tokens per session scan A df9fcde57020

Subscribe to this mod's changes

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.

Related

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…

ommakes/Skills · 123 tokens

release-process

Step-by-step release checklist for Squad — prevents v0.8.22-style disasters.

dotnet/maui-labs · 20 tokens

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…

kvdm-co-pilot/create-cmp · 150 tokens

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…

maxrave-dev/kotlin-footguns · 100 tokens

git-pr-strategy

Apply safe branching, commits, conflict resolution, review ownership, merge, rollback, and release-tag rules.

vmobifystudio/app-dev-team · 26 tokens

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…

buiphucminhtam/forgewright · 65 tokens