Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add devoxx/DevoxxGenieIDEAPlugin --skill releasegit clone --depth 1 https://github.com/devoxx/DevoxxGenieIDEAPluginWrote 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/devoxx/devoxxgenieideaplugin/release)<a href="https://agentmods.dev/skills/devoxx/devoxxgenieideaplugin/release"><img src="https://agentmods.dev/badge/skills/devoxx/devoxxgenieideaplugin/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/devoxx/devoxxgenieideaplugin/release"><img src="https://agentmods.dev/badge/skills/devoxx/devoxxgenieideaplugin/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00121 | $0.01756 |
| Opus 5.5 | $0.00048 | $0.00702 |
| Sonnet 5.5 | $0.00024 | $0.00351 |
| Haiku 4.5 | $0.00012 | $0.00176 |
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 1mo 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release a new DevoxxGenie plugin version
This skill cuts a complete plugin release: version bump → curated changelog → plugin change-notes → build → commit → tag → GitHub release. The goal is a release whose CHANGELOG.md, plugin.xml change-notes, and GitHub release body all tell the same story, written from the actual work done — not a raw dump of PR titles.
The release commit lands on the current default branch (master), matching how prior
releases were cut here. Do not create a feature branch for a release.
Step 1 — Ask for the target version
Never assume the next version. Show the current version and ask the user what to release.
grep -E '^version\s*=' build.gradle.kts | head -n1 # e.g. version = "1.7.4"
Offer patch / minor / major as a guide (e.g. current 1.7.4 → patch 1.7.5, minor
1.8.0, major 2.0.0) but let the user state the exact number. Use it verbatim as
X.Y.Z (tags are vX.Y.Z).
Step 2 — Gather the history since the last release
Find the previous tag, then read what actually changed. You need the substance of each change, so look at PR titles and bodies/commits, not just subject lines.
git describe --tags --abbrev=0 # previous tag, e.g. v1.7.4
git log <prev-tag>..HEAD --oneline # commits to summarise
gh pr list --state merged --base master --limit 30 \
--json number,title,author,mergedAt,body # PR detail + authors
Group changes into the sections the CHANGELOG already uses, by conventional-commit prefix:
| Prefix | CHANGELOG section |
|---|---|
feat / add |
Added |
fix |
Fixed |
refactor / build / perf / style / chore (non-dep) |
Changed |
docs |
Documentation |
test |
Tests |
chore(deps) / bump / upgrade |
Dependencies |
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.
- 1mo ago First seen · 163 lines · 121 tokens per session scan A 2fb673e83406
release is a skill published in the GitHub repository devoxx/DevoxxGenieIDEAPlugin (685 stars, last pushed 2d ago), licensed MIT. It adds 121 tokens to every session and 1,756 once invoked, about $0.0005 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.
Other skills, from other repositories
release
Use this skill for EVERY ClawRouter release. Enforces the full checklist — version sync, CHANGELOG, build, tests, npm publish, git tag, GitHub release. No step can be skipped.
version-bump
Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. Ends with the agent running npm publish itself using the maintainer's npm…
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
changelog
Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions.
team-release
Orchestrate the release team — release-manager, qa-lead, devops-engineer, producer — to execute a release from candidate to deployment.