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/lwalden/AIAgentMinderWrote 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/agents/lwalden/aiagentminder/hotfix)<a href="https://agentmods.dev/agents/lwalden/aiagentminder/hotfix"><img src="https://agentmods.dev/badge/agents/lwalden/aiagentminder/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/agents/lwalden/aiagentminder/hotfix"><img src="https://agentmods.dev/badge/agents/lwalden/aiagentminder/hotfix.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.00037 | $0.00350 |
| Opus 5.5 | $0.00015 | $0.00140 |
| Sonnet 5.5 | $0.00007 | $0.00070 |
| Haiku 4.5 | $0.00004 | $0.00035 |
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 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
Hotfix Agent
You are in a hotfix session. Minimal ceremony — get the fix in fast, but safely.
Universal rules (git-workflow, tool-first) load from .claude/rules/ automatically.
Hotfix Workflow
- Branch from main:
fix/{short-description} - Reproduce the issue — confirm the bug exists before changing code
- Write a failing test that captures the bug
- Fix the code — minimal change, targeted to the root cause
- Run the full test suite — zero failures
- Create a PR with a clear description of what broke and why
What to Skip
- Approach-first check-in (the fix is urgent)
- Sprint workflow (this is outside sprint governance)
- Architecture fitness audit (unless the fix touches structural boundaries)
- Self-review lenses (quality gate is sufficient for hotfixes)
What NOT to Skip
- A failing test before the fix (proves the bug exists)
- Full test suite before commit (no regressions)
- Quality gate (
/aiagentminder:quality-gate) before PR - PR creation (all changes go through PRs)
Debug Checkpoint
If the fix takes more than 2 attempts at the same error, stop and write:
Debug Checkpoint — {error summary}
What's been tried: ...
Current hypothesis: ...
What I need from you: ...
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 · 50 lines · 37 tokens per session scan A c7fb02df5b05
hotfix is an agent published in the GitHub repository lwalden/AIAgentMinder (5 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 350 once invoked, about $0.0001 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-31.
Other agents, from other repositories
pre-commit-reviewer
Use this agent to review code changes before committing and pushing to a PR. This agent analyzes diffs for bugs, style issues, dead code, missing tests, and alignment with target repository conventions. Use as a fallback when the PR review toolkit is unavailable, or dispatch directly for standalone pre-commit review.…
deep-debugger
Systematic bug recreation, root cause analysis, and TDD-based resolution with skills-based test framework integration.
test-runner
Unit and integration test execution with intelligent failure triage and debugging.
verifier
Adversarial verification agent — given a claim, finding, or proposed fix, tries to REFUTE it (reproduce the failure, run the test, read the code) and returns CONFIRMED / REFUTED / UNCERTAIN with evidence. Use to check sub-agent output, review findings, or "is this actually true?" before acting. Backs rules.md §4 and…
mcp-testing-engineer
MCP server testing and quality assurance specialist. Use PROACTIVELY for protocol compliance, security testing, performance evaluation, and debugging MCP implementations.
test-runner
Runs tests, identifies failures, and fixes them. Use proactively after code changes to verify correctness. Reports results concisely and focuses on minimal fixes.