Borrowing it
Nothing to install: this file belongs to blockscout/frontend. 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/blockscout/frontend/main/.agents/skills/prepare-release/SKILL.mdgit clone --depth 1 https://github.com/blockscout/frontendWrote 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/blockscout/frontend/prepare-release)<a href="https://agentmods.dev/skills/blockscout/frontend/prepare-release"><img src="https://agentmods.dev/badge/skills/blockscout/frontend/prepare-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.1 | $0.00029 | $0.02915 |
| Opus 5 | $0.00015 | $0.01458 |
| Sonnet 5 | $0.00006 | $0.00583 |
| Haiku 4.5 | $0.00003 | $0.00292 |
Grade A, and why
prepare-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 2d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What ships with it
2 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.
- 2d ago First seen · 147 lines · 29 tokens per session scan A fbad36a6a0f0
prepare-release is a skill published in the GitHub repository blockscout/frontend (304 stars, last pushed yesterday), with no licence file. It adds 29 tokens to every session and 2,915 once invoked, about $0.0001 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
git-workflow
Git branch management, commit conventions, and PR creation workflow. Use for all tasks that require code changes, regardless of language or scope.
fix-pr-review
Address PR review comments by selecting appropriate skills based on modified files. Use when fixing review feedback on pull requests.
db-migration
Database schema and migration workflow. Use when modifying database schemas in tools/atlas/ or SQLC queries in tools/sqlc/.
github-issue-creation
Create GitHub issues with proper task classification. Classification determines which Skills will be used when working on the issue.
doc-changelog-writer
Generate CHANGELOG.md entries from git commits.
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled…