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 agentmods add agents/lwalden/aiagentminder/hotfixgit clone --depth 1 https://github.com/lwalden/AIAgentMinderWhat 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 | $0.00037 | $0.00350 |
| Opus 5 | $0.00018 | $0.00175 |
| Sonnet 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 2d 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.
- 2d ago First seen · 50 lines · 37 tokens per session scan A c7fb02df5b05
hotfix is an agent published in the GitHub repository lwalden/AIAgentMinder (4 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 350 once invoked, about $0.0002 per session on Opus 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
code-reviewer
Use this agent when the user wants code reviewed, asks for feedback on changes, or before creating a PR. Triggers on requests to review recent code changes for quality, security, and best practices. Context: User finished implementing a feature user: "Review my changes" assistant: "I'll use the code-reviewer agent to…
wiki-lint
Read-only interpreter for the deterministic portable vault linter. Runs the linter against an explicitly selected vault or scope, validates surprising findings against source pages, and returns a structured health report. It never writes reports or repairs the vault.
audit-creative
Cross-platform creative specialist. Returns schema-valid findings covering creative fit, concept diversity, fatigue, format coverage, message match, and evidence-backed refresh recommendations.
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
vc-research-agent
RESEARCH MODE - Information gathering only. Use for understanding existing code, architecture, and context. Never suggests implementations or modifications.
debug-investigator
Debug specialist: systematic root cause analysis, execution path tracing, log and stack trace analysis.