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/fl-sean03/opensdl/releasenpx skills add fl-sean03/OpenSDL --skill releasegit clone --depth 1 https://github.com/fl-sean03/OpenSDLWrote 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/fl-sean03/opensdl/release)<a href="https://agentmods.dev/skills/fl-sean03/opensdl/release"><img src="https://agentmods.dev/badge/skills/fl-sean03/opensdl/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.00041 | $0.00491 |
| Opus 5 | $0.00020 | $0.00246 |
| Sonnet 5 | $0.00008 | $0.00098 |
| Haiku 4.5 | $0.00004 | $0.00049 |
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 4d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build a release candidate
This procedure ends at built artifacts in dist/. It does not upload to a package index, sign an
artifact, generate an SBOM, create a Git tag, or create a GitHub Release, and neither does
.github/workflows/release.yml, which runs the same gate on a clean runner and uploads the
distributions as an expiring Actions artifact. Nothing has ever been published or tagged. What
publishing would additionally require, and what it costs irreversibly, is written down in
releasing and publishing; do not improvise it here.
Inputs
- target version
- reviewed release scope and notes
Procedure
- Start from a clean worktree and an absent or empty
dist/. Review changes since the previous release — there is not yet a first one, so the scope is the whole history until there is. - Run
.agents/skills/release/run.sh VERSION. - Review synchronized workspace versions, installed CLI and API version reporting, citation metadata, generated dependency floors, public API changes, schemas, and migration guidance.
- Do not recreate the import-evidence files at the repository root. They describe the imported
snapshot and live at the import commit;
docs/development/import-provenance.mdrecords where and why. - Inspect every wheel and source archive under
dist/. - Record the exact validation evidence and unresolved release work.
Completion
All workspace distributions build from the reviewed revision, and the test, lint, type, schema, boundary, example, and conformance checks pass. The artifacts are local and unpublished.
Stop conditions
Stop on a dirty worktree, a nonempty dist/, a failing check, an unexpected public API change, or
an unexpected artifact.
Stop and hand back to the repository owner before any step that leaves the machine: registering a project name, configuring a trusted publisher, uploading a distribution, or pushing a tag. Claiming a name on a package index cannot be undone, and an uploaded version can never be re-uploaded.
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.
- 4d ago First seen · 46 lines · 41 tokens per session scan A 41f2af4d6332
release is a skill published in the GitHub repository fl-sean03/OpenSDL (102 stars, last pushed 4d ago), licensed Apache-2.0. It adds 41 tokens to every session and 491 once invoked, about $0.0002 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
scitex
Skill "scitex" from scitex-ai/scitex-python, covering scitex — umbrella package, mechanics, sub-skills index, quick reference and mandatory leaves.
stx.cli
Command-line interface for SciTeX platform operations — 30+ subcommands with lazy loading. Specialization of scitex-cli-convention.
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.
changelog-entry
Add a new entry to CHANGELOG.yml under the current unreleased version (or create the version block if needed), then regenerate documentation. Use when the user says things like "add a changelog entry", "log this fix in the changelog", or "/changelog-entry".
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.
snapshot-release
Drives the snapshot-release flow for the current branch's PR. Posts a /snapshot comment on the PR if one isn't already there (with confirmation), waits for the Continuous Releases workflow to finish, and reports the tarball URLs from the resulting 📦 Snapshot Release comment. Use for both triggering and waiting …