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/akurinnoy/ok_pluginsWrote 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/plugins/akurinnoy/ok_plugins/ok-prerelease-verification)<a href="https://agentmods.dev/plugins/akurinnoy/ok_plugins/ok-prerelease-verification"><img src="https://agentmods.dev/badge/plugins/akurinnoy/ok_plugins/ok-prerelease-verification/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/plugins/akurinnoy/ok_plugins/ok-prerelease-verification"><img src="https://agentmods.dev/badge/plugins/akurinnoy/ok_plugins/ok-prerelease-verification.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ok-prerelease-verification 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.
The source is not reproduced here
Licensed EPL-2.0
The repository is licensed EPL-2.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 121 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 First seen · 8 lines scan A b5fa0da496e4
ok-prerelease-verification is a plugin published in the GitHub repository akurinnoy/ok_plugins (3 stars, last pushed 10d ago), licensed EPL-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-31.
Other plugins, from other repositories
ship
End-to-end shipping workflow: smart staging with change cohesion analysis, conventional commits, test gates, push, and optional PR creation.
dev
Back half of the development flow, from a PR ready for review to merge and cleanup; the front half (idea -> spec -> tickets -> PR) belongs to Matt's skills (mattpocock-skills). GitHub workflow: commit-and-push, release, review-loop (unified CodeRabbit + ChatGPT-Codex review loop with autonomous apply/defer/skip…
delivery-lab
Adds release-readiness, regression, and session-recap workflows plus a quality-gate MCP bundle.
dev-workflow
Development workflow commands and agents for commits, tests, docs, and changelogs.
craft
Full-stack developer toolkit with integrated workflow automation - 48 commands, 2 agents, 41 skills with standardized dry-run preview mode (29 with --dry-run support). Code, git, site, docs, testing, architecture, CI, distribution, teaching workflows, planning, release pipeline, and ADHD-friendly features including…
atlas-publish
Takes the open PRs of the Atlas/Bella monorepo to a registered draft release on either the over-the-air or the App Store lane, classifying between them from the expo-updates native fingerprint rather than from intent — ios.buildNumber sits inside that fingerprint, so a buildNumber bump alone forces a store release.…