Borrowing it
Nothing to install: this file belongs to MarcoPorcellato/matryca-plumber. 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/MarcoPorcellato/matryca-plumber/main/.agents/skills/matryca-release/SKILL.mdgit clone --depth 1 https://github.com/MarcoPorcellato/matryca-plumberWrote 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/marcoporcellato/matryca-plumber/matryca-release)<a href="https://agentmods.dev/skills/marcoporcellato/matryca-plumber/matryca-release"><img src="https://agentmods.dev/badge/skills/marcoporcellato/matryca-plumber/matryca-release.svg" alt="Measured on agentmods" 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.00050 | $0.00122 |
| Opus 5 | $0.00025 | $0.00061 |
| Sonnet 5 | $0.00010 | $0.00024 |
| Haiku 4.5 | $0.00005 | $0.00012 |
Grade A, and why
matryca-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 8d 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.
What it actually says
Matryca release
Read .cursor/rules/05-release-preparation.mdc completely before acting. Also use the changelog and GitHub workflow skills for their respective parts. Never tag, push, merge, or publish without explicit user authorization.
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.
- 8d ago First seen · 8 lines · 50 tokens per session scan A 3bd2803713d5
matryca-release is a skill published in the GitHub repository MarcoPorcellato/matryca-plumber (97 stars, last pushed yesterday), licensed Apache-2.0. It adds 50 tokens to every session and 122 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-30.
Other skills, from other repositories
create-release
Create a new software release with planning, manifest, and execution schedule. Use when the user mentions creating a release, planning a release, \\"new release\\", version numbers like \\"v1.0.0\\", or release-related planning. Can be invoked via /create-release.
git-workflow
When the user asks you to perform git operations, create branches, open PRs, manage releases, or resolve conflicts, follow this guide. These are the procedural patterns you should apply consistently.
struthio
Skill "struthio" from markmhendrickson/ateles, covering struthio — autonomous release agent, identity, principals, core job and release execution steps.
verify-deployment
Check GitHub Actions after a website deploy and fix or re-run until the build succeeds. Use after a deploy push or when user says \\"check deploy\\", \\"verify deployment\\", or \\"did the build succeed\\". Can be invoked via /verify-deployment.
publish
Publish workflow per foundation publish command.
release-prep
Prepare release documentation including CHANGELOG entry, announcement text, and validation. Run before tagging a new release.