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/optimiziramsi/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/plugins/optimiziramsi/skills/hotfix)<a href="https://agentmods.dev/plugins/optimiziramsi/skills/hotfix"><img src="https://agentmods.dev/badge/plugins/optimiziramsi/skills/hotfix/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/optimiziramsi/skills/hotfix"><img src="https://agentmods.dev/badge/plugins/optimiziramsi/skills/hotfix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
hotfix 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 12d 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
{
"name": "hotfix",
"displayName": "optimiziramsi hotfix",
"version": "0.1.0",
"description": "Test-first hotfix for a deployed bug — reproduce as a failing test, minimal fix, land it on both the mainline and the release branch.",
"author": {
"name": "optimiziramsi",
"url": "https://github.com/optimiziramsi"
},
"homepage": "https://github.com/optimiziramsi/skills/tree/main/hotfix#readme",
"repository": "https://github.com/optimiziramsi/skills",
"license": "MIT",
"keywords": [
"git",
"hotfix",
"release"
]
}
What it installs
The manifest is a name and a version. 1 skill, 1 command travel with it, and installing the plugin installs all of them — 157 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.
- 12d ago First seen · 19 lines scan A e419fb65b35d
hotfix is a plugin published in the GitHub repository optimiziramsi/skills (2 stars, last pushed 2d ago), licensed MIT. 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-10-19.
Other plugins, from other repositories
flow
Skill-driven workflow plugin for GitHub development with excellence-by-default quality gates. Encodes team knowledge as composable skills, enforces safety through hooks, and compounds learning across sessions. Strict TDD, Stranger Test, holdout validation, and evidence-based verification built in. Durable goals…
whetstone
Engineering-craft skills: red-green TDD, flaky-test audit, diagnosis, doubt review, grilling, merge-conflict resolution, research reports with grounded claims, HTML reports, skill linting and a column budget. Every gate among them carries a deterministic self-verify.
engineering-practices
Git commits, conventional releases, refactoring, test-driven development, and engineering ways of working skills.
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…
es6kr
Reusable AI coding skills: TDD, commit management, dotfile sync, and more.
quatico-skills
Quatico development essentials: commit conventions, PR workflows, TDD, testing, Bitbucket/Jira integration, and team standards.