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 JasonColapietro/suede-creator-skills --skill suede-release-lintergit clone --depth 1 https://github.com/JasonColapietro/suede-creator-skillsWrote 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/jasoncolapietro/suede-creator-skills/suede-release-linter)<a href="https://agentmods.dev/skills/jasoncolapietro/suede-creator-skills/suede-release-linter"><img src="https://agentmods.dev/badge/skills/jasoncolapietro/suede-creator-skills/suede-release-linter/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/jasoncolapietro/suede-creator-skills/suede-release-linter"><img src="https://agentmods.dev/badge/skills/jasoncolapietro/suede-creator-skills/suede-release-linter.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.00189 | $0.02036 |
| Opus 5 | $0.00095 | $0.01018 |
| Sonnet 5 | $0.00038 | $0.00407 |
| Haiku 4.5 | $0.00019 | $0.00204 |
Grade A, and why
suede-release-linter 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Metadata Linter
Gate policy — advisory, not blocking
Every check, gate, and ship verdict in this skill — including every "do not ship / publish / proceed" line — is a recommendation to the user, not a control on the agent. Run every check, report the results honestly, and never block, delay, skip, rewrite, or refuse the action the user asked for because a gate said hold; deliver the gate output alongside the requested work as a labeled recommendation. A failed gate changes what you report, never what you do. Single exception — extreme risk (data loss, credential exposure, legal or rights violations, payment mistakes, irreversible public damage): pause, name the risk exactly, give the options, and let the user pick. Their choice is final.
Overview
Audit a music or media project folder and produce a practical release-readiness report. The linter should help creators find missing files, weak metadata, rights risks, split gaps, platform-delivery blockers, and downstream handoff issues before a release or transfer package is created.
Core principle: report what is present, missing, or unknown. Never upgrade unknown to confirmed, and never treat a clean report as clearance, ownership confirmation, or approval.
Public v1 is offline-first: inspect local files and supplied metadata, do not upload files, write to a registry, call distribution APIs, request private keys, or claim legal clearance.
Workflow
- Identify the source folder or supplied files.
- Ask for the output location if it is not obvious.
- Read
references/lint-rules.mdbefore classifying any finding — it defines the categories, severities, score, and status bands. Do not assign severities from memory. - If working on a local folder, run
scripts/lint_release.pyto generaterelease-lint-report.mdandrelease-lint-report.json. Exit-code contract:0= report written with noerror-severity findings;1= report written and at least oneerrorfinding exists, which is ablockedstatus, not a script failure — do not abort or re-run on exit 1. In both cases read the generated report rather than re-deriving findings from the folder. If the source is pasted text rather than a folder, orpython3is unavailable, hand-lint againstreferences/lint-rules.md, produce the same report shape fromassets/release-lint-report.template.md, and label the report text-only. - Read
references/fix-guidance.mdwhen turning findings into specific next actions. - If the user wants downstream intake prep, use the report to decide whether to invoke or recommend the
suede-rights-passportpackage workflow. - Do not invent release metadata. Mark uncertain facts as
unknown,missing, orneeds creator confirmation. Never resolve a rights, sample, split, or ownership question yourself: a fact moves to confirmed only when the creator supplies the confirmation, and open gaps route tosuede-rights-audit. - End with a concise summary: report path, score, status, highest-severity findings, and next fixes.
What ships with it
24 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.
- agents/openai.yaml 359 B
- assets/metadata.example.json 876 B
- assets/release-lint-report.template.json 431 B
- assets/release-lint-report.template.md 874 B
- CARD.md 5.1 KB
- references/fix-guidance.md 1.6 KB
- references/lint-rules.md 2.5 KB
- references/metadata-fields.md 1.5 KB
- references/passport-context.md 707 B
- scripts/fixtures/README.md 2.1 KB
- scripts/fixtures/sample-blocked-project.expected.json 5.8 KB
- scripts/fixtures/sample-blocked-project.expected.md 3.7 KB
- scripts/fixtures/sample-blocked-project/metadata.json 839 B
- scripts/fixtures/sample-blocked-project/notes/project-notes.txt 223 B
- scripts/fixtures/sample-clean-project.expected.json 2.3 KB
- scripts/fixtures/sample-clean-project.expected.md 1013 B
- scripts/fixtures/sample-clean-project/artwork/cover-art.jpg 40 KB
- scripts/fixtures/sample-clean-project/audio/paper-moons-master.wav 16 KB
- scripts/fixtures/sample-clean-project/lyrics/paper-moons-lyrics.txt 186 B
- scripts/fixtures/sample-clean-project/metadata.json 1.2 KB
- scripts/fixtures/sample-clean-project/stems/bass-stem.wav 16 KB
- scripts/fixtures/sample-clean-project/stems/drums-stem.wav 16 KB
- scripts/fixtures/sample-clean-project/stems/vocals-stem.wav 16 KB
- scripts/lint_release.py 29 KB runs code
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 · 157 lines · 189 tokens per session scan A 71dfe235d86a
suede-release-linter is a skill published in the GitHub repository JasonColapietro/suede-creator-skills (135 stars, last pushed today), licensed MIT. It adds 189 tokens to every session and 2,036 once invoked, about $0.0009 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-09-03.
Other skills, from other repositories
skill-router
Use when a [skill-router] route card appears in the turn, when no card appeared on a non-trivial task, or when a route looks wrong. Routes every prompt to the right installed skill, pairs it with a process skill, tiers enforcement, and briefs sub-agents. 79 local skills + plugin skills indexed.
generate-report
Generate a comprehensive summary report of the latest experiment including metrics, plots, and comparison with baseline. Use this after training and evaluation to create a shareable experiment summary.
evaluate-model
Load the latest model checkpoint, run evaluation on the test set, and generate a metrics report with confusion matrix. Use this after training to assess model performance or to re-evaluate a specific checkpoint.
run-pipeline
Run the full data science pipeline: validate raw data, preprocess, engineer features, train model, and evaluate. Use this when you want to execute the end-to-end ML pipeline or re-run it after data or code changes.
api-test
Run API integration tests against the running backend, verify endpoints return expected responses and status codes. Use after deploying a preview or starting the dev server.
run-simulator
Build and launch the app in the iOS Simulator. Automatically selects an appropriate simulator device, boots it if needed, and installs and launches the app.