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 agentmods add skills/reboulip/rblclass/make-releasenpx skills add reboulip/rblclass --skill make-releasegit clone --depth 1 https://github.com/reboulip/rblclassWrote 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/reboulip/rblclass/make-release)<a href="https://agentmods.dev/skills/reboulip/rblclass/make-release"><img src="https://agentmods.dev/badge/skills/reboulip/rblclass/make-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 | $0.00082 | $0.03257 |
| Opus 5 | $0.00041 | $0.01629 |
| Sonnet 5 | $0.00016 | $0.00651 |
| Haiku 4.5 | $0.00008 | $0.00326 |
Grade A, and why
make-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 3d 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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/make-release — ship the RBLclass product
Produce, from one command, both shippable artifacts for the actual product (not the POC):
- an install kit (
.zip) that can be copied to a target workstation and installed without admin rights — the originally-validated path and documented fallback; and - the per-user MSI (
installer\bin\RBLclass-<version>.msi) — the artifact end users actually receive and double-click, as described in the trilingual pilot install guide (docs/installation-guide.html).
Both are built from the same Release output and the same
release.config.json identity, so they can never carry different
versions or COM identities. CLAUDE.md ("Packaging") has them coexist
until the MSI is also validated by install/uninstall on the real 32-bit
target — at that point the kit can retire.
This skill encodes the release/packaging workflow that used to live in
CLAUDE.md ("Build and run" / "Publishing"). The proven mechanics are
adapted from the validated Phase 0 POC staging flow; the MSI build reuses
the declarative WiX packaging added alongside it
(installer/Package.wxs + installer/Build-Installer.ps1).
Scope
- In scope: the Phase 1 product —
RBLclass.sln,src/RBLclass.AddIn(+.Core,.Outlook.Adapter). Package formats produced in one run: PowerShell install kit (build → stage → verify both native SQLite bitnesses → AES-256 zip) and the WiX MSI (same Release build →wix buildagainstinstaller/Package.wxs).
Preconditions (check before running, fail clearly)
- Branch. Work on
developor a branch off it (repo rule). - Product exists.
RBLclass.slnmust exist at the repo root andsrc/RBLclass.AddInmust build. If it does not, the product has not been built yet — stop and tell the user the release cannot be produced until the solution exists. - COM identity reconciled. Open the add-in class in
src/RBLclass.AddInand confirm its[Guid(...)]and[ProgId(...)]matchClsid/ProgIdin release.config.json, along withAssemblyName,AssemblyClass,AssemblyVersion. The config ships with an all-zeros sentinelClsid; every script in this skill (andinstaller\Build-Installer.ps1) refuses to run until you replace it with the real values. This is the one-time reconciliation the first real release requires. - Tooling. Visual Studio 2022 (MSBuild, located via vswhere) + the
standalone .NET SDK on PATH. 7-Zip for the encrypted zip (or pass
-Password ''for a plain zip). ThewixCLI for the MSI step — a per-user dotnet global tool:dotnet tool install --global wix(then re-open the shell so%USERPROFILE%\.dotnet\toolsis on PATH).
What ships with it
4 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.
- 3d ago First seen · 276 lines · 82 tokens per session scan A 2aae17c5fb59
make-release is a skill published in the GitHub repository reboulip/rblclass (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 82 tokens to every session and 3,257 once invoked, about $0.0004 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
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.
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
greptimedb-release
Runbook for publishing a new GreptimeDB version (tag + GitHub release + docs release-note PR) on the upstream GreptimeTeam/greptimedb repo. Use when asked to "release" / "publish" a GreptimeDB version (e.g. v1.1.0, v1.0.3).
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…
publish-registry
Publish @agentos-software/ registry packages from AgentOS. Use whenever the user asks to publish or release registry software/agent packages.
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.