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 skills add andrewvaughan/agent-council --skill hotfixgit clone --depth 1 https://github.com/andrewvaughan/agent-councilWrote 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/skills/andrewvaughan/agent-council/hotfix)<a href="https://agentmods.dev/skills/andrewvaughan/agent-council/hotfix"><img src="https://agentmods.dev/badge/skills/andrewvaughan/agent-council/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/skills/andrewvaughan/agent-council/hotfix"><img src="https://agentmods.dev/badge/skills/andrewvaughan/agent-council/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.00059 | $0.01230 |
| Opus 5 | $0.00030 | $0.00615 |
| Sonnet 5 | $0.00012 | $0.00246 |
| Haiku 4.5 | $0.00006 | $0.00123 |
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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hotfix Workflow
Apply an urgent fix through a streamlined pipeline that skips the full planning cycle. This skill is for production bugs, security patches, and critical regressions.
[!CAUTION] This is NOT a shortcut for feature work. If the change adds new functionality, changes user-facing behavior, or touches more than ~100 lines, use
/plan-featureinstead. Hotfixes should be small, focused, and clearly scoped.
[!CAUTION] Scope boundary: This skill implements the fix, reviews it, creates a PR, and monitors CI. It covers the full lifecycle for urgent fixes so the user does not need to chain multiple skills.
Step 1: Define the Fix
CHECKPOINT: Confirm Hotfix Scope
Ask the user to describe the issue. Gather:
- What is broken? (symptom, error message, affected users)
- Where is the bug? (file, endpoint, component — if known)
- How urgent? (production down, data corruption, security vulnerability, degraded experience)
- GitHub issue number (if one exists)
If the user provides a GitHub issue number, fetch it:
gh issue view <number> --json title,body,labels,state,number
Present a summary and ask the user to confirm this is appropriate for hotfix (not a feature).
Step 2: Create Branch and Investigate
-
Ensure you are on
mainand up to date:git fetch origin git checkout main git pull origin main -
Create a
fix/branch:git checkout -b fix/<short-description> -
If a GitHub issue exists, add the
in-progresslabel (following AGENTS.md label management rules — remove from any other issue first). -
Investigate the bug: read relevant files, reproduce the issue if possible, identify the root cause.
Present the root cause analysis to the user before proceeding.
Step 3: Apply the Fix
-
Make the minimal change needed to resolve the issue.
-
Write or update tests to cover the bug (regression test).
-
Run self-checks:
pnpm type-check pnpm lint pnpm test
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.
- 9d ago First seen · 172 lines · 59 tokens per session scan A 7d8410161266
hotfix is a skill published in the GitHub repository andrewvaughan/agent-council (13 stars, last pushed 6mo ago), licensed MIT. It adds 59 tokens to every session and 1,230 once invoked, about $0.0003 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-30.
Other skills, from other repositories
dev-doctor
Run a development-focused health check on the AIWG repository structure.
config-validator
Validate AIWG configuration files and project setup for correctness and completeness.
aiwg-pr
AIWG-specific pull request delivery workflow for AIWG product/workspace changes; not the generic repository PR process.
artifact-metadata
Manage artifact metadata, versioning, ownership, and review history across the SDLC lifecycle.
commit-and-push
Create a well-formatted git commit and push to remote repository.
customize-setup
Set up personal AIWG customization mode from a local clone or fork — makes your clone the live global AIWG instance so edits go live immediately.