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.
git clone --depth 1 https://github.com/ustoppble/overclickWrote 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/commands/ustoppble/overclick/release)<a href="https://agentmods.dev/commands/ustoppble/overclick/release"><img src="https://agentmods.dev/badge/commands/ustoppble/overclick/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/commands/ustoppble/overclick/release"><img src="https://agentmods.dev/badge/commands/ustoppble/overclick/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.00012 | $0.00140 |
| Opus 5.5 | $0.00005 | $0.00056 |
| Sonnet 5.5 | $0.00002 | $0.00028 |
| Haiku 4.5 | $0.00001 | $0.00014 |
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 1mo 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
Load the bundled overclick skill and read its linked canonical OVERCLICK.md.
Find this session's single executing card with task_list
using status: "em_execucao", claimed_by: "me", and the session_id declared
in this session's claim. Refuse an unknown session. Treat $ARGUMENTS as the
exact release tag and call task_update with resolved_in. Refuse an empty tag
or an ambiguous set of active claims. This command does not validate or deploy
the card.
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.
- 1mo ago Changed · +1 lines faac91de6b0f
- 2mo ago First seen · 12 lines · 12 tokens per session scan A d66158aaca55
release is a command published in the GitHub repository ustoppble/overclick (119 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 140 once invoked, about $0.0000 per session on Opus 5.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 commands, from other repositories
changelog
Generate a changelog entry from git commits since the last tag using conventional commit format.
lavra-ship
Fully automated ship sequence from code-ready to PR-open with beads closed and knowledge captured.
changelog
Create engaging changelogs for recent merges to main branch.
release-checklist
Obsolète (retirée en 9.0) : utilisez /gate:check release.
changelog
Add user-facing features since the last release to CHANGELOG.md, under the given next version. Run before cutting a release.
hatch3r-release
Release-workflow orchestrator — preflight, SemVer bump, changelog sync, build + CycloneDX SBOM, adapter-output verification, quality gates, release-notes reconciliation, then stop before publish/merge for human approval.