Borrowing it
Nothing to install: this file belongs to Mistakey/simulink-automation-suite. 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/Mistakey/simulink-automation-suite/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/Mistakey/simulink-automation-suiteWrote 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/mistakey/simulink-automation-suite/release)<a href="https://agentmods.dev/skills/mistakey/simulink-automation-suite/release"><img src="https://agentmods.dev/badge/skills/mistakey/simulink-automation-suite/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/mistakey/simulink-automation-suite/release"><img src="https://agentmods.dev/badge/skills/mistakey/simulink-automation-suite/release.svg" alt="Reviewed on agentmods" width="80" 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.00052 | $0.01589 |
| Opus 5 | $0.00026 | $0.00794 |
| Sonnet 5 | $0.00010 | $0.00318 |
| Haiku 4.5 | $0.00005 | $0.00159 |
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 9d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
Default release path is tag-driven GitHub auto release via .github/workflows/release.yml.
Files to Check First
.claude-plugin/plugin.json.claude-plugin/marketplace.jsonsimulink_cli/core.py—build_schema_payload()["version"]docs/release/scripts/check_release_metadata.pyscripts/build_release_notes.py.github/workflows/release.yml
Release Flow
- Pick version
X.Y.Z - Update manifests and schema:
.claude-plugin/plugin.json→version: "X.Y.Z".claude-plugin/marketplace.json→plugins[0].version: "X.Y.Z"simulink_cli/core.py→build_schema_payload()["version"]to"X.Y"(only when major.minor changes)docs/release/<date>-vX.Y.Z.mdwhen required (see Release Notes section)
- Validate locally:
python scripts/check_release_metadata.py --tag vX.Y.Z
python -m unittest tests.test_plugin_manifest_contract tests.test_marketplace_manifest_contract -v
python -m unittest discover -s tests -p "test_*.py" -v
claude plugin validate .
python scripts/build_release_notes.py --tag vX.Y.Z --ref HEAD
-
Archive live test report (if available):
- If
docs/reports/LIVE-TEST-REPORT.mdexists:- Check report's
Test Commitvs current HEAD - If close match: copy to
docs/reports/archive/live-test-vX.Y.Z.md - If large gap: warn "Live test report may be stale" — user decides
- Reference archived report in release notes Validation section
- Check report's
- If no report exists: warn "No live test report. Consider running /live-test first." — do not block release
- If
-
Commit release changes
-
Create and push annotated tag:
git tag -a vX.Y.Z -m "Release vX.Y.Z"
git push origin <branch>
git push origin vX.Y.Z
.github/workflows/release.ymlcreates the GitHub Release automatically
Version Sync Rules
For release version X.Y.Z, all four must match:
| Location | Required Value |
|---|---|
.claude-plugin/plugin.json → version |
X.Y.Z |
.claude-plugin/marketplace.json → plugins[0].version |
X.Y.Z |
simulink_cli/core.py → build_schema_payload()["version"] |
X.Y |
| Git tag | vX.Y.Z |
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.
- 9d ago First seen · 167 lines · 52 tokens per session scan A 221369114212
release is a skill published in the GitHub repository Mistakey/simulink-automation-suite (9 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 1,589 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-31.
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.
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.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
updater_guide
Guidance for checking for and installing Row-Bot updates.