Borrowing it
Nothing to install: this file belongs to ingo-eichhorst/Irrlicht. 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/ingo-eichhorst/Irrlicht/main/.claude/skills/ir:release/SKILL.mdgit clone --depth 1 https://github.com/ingo-eichhorst/IrrlichtWrote 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/ingo-eichhorst/irrlicht/ir-release)<a href="https://agentmods.dev/skills/ingo-eichhorst/irrlicht/ir-release"><img src="https://agentmods.dev/badge/skills/ingo-eichhorst/irrlicht/ir-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.00083 | $0.19649 |
| Opus 5 | $0.00042 | $0.09824 |
| Sonnet 5 | $0.00017 | $0.03930 |
| Haiku 4.5 | $0.00008 | $0.01965 |
Grade E, and why
ir:release scanned grade E with 4 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 2d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
no cgo. **Required** — omitting them makes every Linux `curl … | sh` 404 on Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf /tmp/irrlichd-tarball && mkdir -p /tmp/irrlichd-tarball/web Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
> then `curl 127.0.0.1:7839/ | grep '<title>'` (covers the v0.4.4 missing-web bug). Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
prev = os.environ.get('PREV_TAG') or subprocess.check_output( How it starts
The opening of the file, as written. The whole thing — 1,362 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Irrlicht Release
Build and publish a complete irrlicht release. Run all steps back-to-back without pausing.
The argument (if any) is the bump type: patch (default), minor, or major.
Step 1: Determine Version
-
Read
version.jsonfor the current version. -
Bump according to the argument (default
patch):patch: 0.2.3 → 0.2.4minor: 0.2.3 → 0.3.0major: 0.2.3 → 1.0.0
-
Set
$NEW_VERSIONfor all subsequent steps. -
Capture the release base SHA — load-bearing for the race guard in Step 7b. The Swift build + DMG packaging takes ~5 minutes; a maintainer PR squash-merged during that window will silently end up on top of the release commit, included in the v$NEW_VERSION tree but absent from the release notes and built against stale artifacts. v0.4.5 shipped through exactly this race (PR #379 landed mid-build; required an amend PR + a force-pushed tag to recover).
git fetch origin main BASE_SHA=$(git rev-parse origin/main) echo "$BASE_SHA" > /tmp/irrlicht-release-base.sha echo "release base: $BASE_SHA"Keep
BASE_SHA(or the file) accessible through Step 7b. Step 7b's race-guard check fails the release iforigin/mainhas moved past it.
Step 1.5: Refresh Model Aliases (codeburn sync)
Run the /ir:refresh-aliases workflow inline — see
.claude/skills/ir:refresh-aliases/SKILL.md for the full procedure — before
drafting release notes so any new frontend aliases ship with this release
instead of waiting another cycle. Follow the file by path rather than
invoking the skill by name: a skill added or renamed after this session
started is not registered in it, so the Skill call is rejected while the
file is right there (#1249). The map in core/pkg/capacity/aliases.go is a hand-translated port of
codeburn's BUILTIN_ALIASES; new entries upstream mean real users on new
frontends (Cursor variants, Antigravity Gemini models, etc.) price at $0
until we sync.
- Fetch upstream and diff against the in-repo map (see
.claude/skills/ir:refresh-aliases/SKILL.mdfor the full workflow). - If the diff is empty: continue to Step 2. No-op is the common case.
- If Added entries exist: append them to
core/pkg/capacity/aliases.goin the appropriate grouping section, preserving the per-group comments. The table-driven test (TestModelAliases_ResolveToCanonical) auto-covers new entries — Step 5 will catch a mistyped canonical. - If Changed entries exist: pause and surface to the maintainer. A canonical-target change is rare (model rename or codeburn correction) and warrants review before shipping.
- If Removed entries exist: leave the local entry in place — codeburn may have dropped something we still need. Note in the release notes if you want to track it.
- If any Added/Changed canonical isn't in LiteLLM's table (check via
~/.local/share/irrlicht/model-capacity-cache.json), the alias still resolves to a zero-value capacity — flag for follow-up but don't block the release.
What ships with it
1 file 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.
- 2d ago Changed · +48 lines a48d867b9f95
- 7d ago First seen · 1,314 lines · 83 tokens per session scan E 34d2285b4def
ir:release is a skill published in the GitHub repository ingo-eichhorst/Irrlicht (97 stars, last pushed yesterday), licensed MIT. It adds 83 tokens to every session and 19,649 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it E with 4 findings (downloads and executes remote code, recursive force delete, makes network calls). 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-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.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
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.