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 Flagrare/agent-skills --skill release-checkgit clone --depth 1 https://github.com/Flagrare/agent-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/flagrare/agent-skills/release-check)<a href="https://agentmods.dev/skills/flagrare/agent-skills/release-check"><img src="https://agentmods.dev/badge/skills/flagrare/agent-skills/release-check.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.00077 | $0.06081 |
| Opus 5 | $0.00039 | $0.03040 |
| Sonnet 5 | $0.00015 | $0.01216 |
| Haiku 4.5 | $0.00008 | $0.00608 |
Grade A, and why
release-check scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s https://pypi.org/pypi/<package>/json | jq -r .info.version The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 419 lines · 77 tokens per session scan A 4969a22b9473
release-check is a skill published in the GitHub repository Flagrare/agent-skills (11 stars, last pushed 5d ago), with no licence file. It adds 77 tokens to every session and 6,081 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
Release Engineering
Semantic versioning, changelog generation, and release/hotfix management so releases are predictable and reversible.
changelog
Use when the user wants to generate a changelog, release notes, or document what changed between versions, tags, or PRs.
mindforge-ship_extended
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup.
github-repo-management
Clone/create/fork repos; manage remotes, releases.
mindforge-complete-milestone
Archive completed milestone and prepare for next version.
changelog
Generate a visual changelog entry for the current PR. Runs git commands and test suites to gather data, outputs structured JSON, rendered by the visual changelog viewer.