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 skills/samibs/skillfoundry/hotfixnpx skills add samibs/skillfoundry --skill hotfixgit clone --depth 1 https://github.com/samibs/skillfoundryWhat 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.00010 | $0.00906 |
| Opus 5 | $0.00005 | $0.00453 |
| Sonnet 5 | $0.00002 | $0.00181 |
| Haiku 4.5 | $0.00001 | $0.00091 |
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.
How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: hotfix description: Emergency fix mode. Bypasses full pipeline. Smoke test only. Creates mandatory follow-up story. color: red
/hotfix — Emergency Fix Pipeline
USE ONLY FOR PRODUCTION INCIDENTS This skill bypasses gates. Every bypass is logged. Every hotfix creates follow-up debt. The follow-up story must be completed via
/featurebefore the incident is closed.
Activation
/hotfix "null pointer crash on checkout when cart is empty"
/hotfix "login endpoint returning 500 on all OAuth callbacks"
/hotfix "memory leak causing OOM kills in the worker pool"
What This Does
/hotfix [description]
Step 0: Declare incident + load execution context
Step 1: Semgrep HARD BLOCK scan (secrets/SQL injection — always active)
Step 2: Implement the minimal fix
Step 3: Smoke test — max 2 iterations (changed files only)
Step 4: Commit with hotfix: prefix + bypass disclosure
Step 5: Create genesis/hotfix-followup-*.md (mandatory)
Step 6: Write audit entry to logs/audit-trail.jsonl
Pipeline Diagram
/hotfix "description"
│
▼
[Step 0] DECLARE INCIDENT ──────── Print bypass list
│
▼
[Step 1] SEMGREP HARD BLOCK ──── ERROR severity only
│ (never bypassed, even in hotfix)
CLEAN BLOCKED
│ │
▼ └── HALT: fix security issue first
[Step 2] IMPLEMENT FIX ─────────── Minimal, no cleanup, read files first
│
▼
[Step 3] SMOKE TEST ─────────────── Max 2 iterations, changed files only
│
PASSING FAILING after 2
│ │
▼ └── Ask: --accept-failing or abort?
[Step 4] COMMIT ─────────────────── hotfix: prefix, bypass disclosure
│
▼
[Step 5] FOLLOW-UP STORY ───────── genesis/hotfix-followup-*.md (MANDATORY)
│
▼
[Step 6] AUDIT TRAIL ────────────── logs/audit-trail.jsonl + logs/hotfixes.md
│
▼
HOTFIX COMPLETE
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 · 131 lines · 10 tokens per session scan A 8ef332f39e2f
hotfix is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 906 once invoked, about $0.0001 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
memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.
memorix-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
ring:applying-composition-patterns
React composition patterns that scale. Avoid boolean prop proliferation by using compound components, lifting state, and composing internals. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or during architecture review. Skip for simple components with 1-2 props…
ring:searching-code
Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…
ring:exploring-codebases
Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…
ring:auditing-dependency-security
Auditing a dependency for supply-chain risk before install (pip/npm/go/cargo): checks typosquatting, maintainer/age risk, vulnerability DBs (OSV, GHSA, Socket), and lockfile hash pinning, then emits a risk score and approve/conditional/escalate/block decision. Use when adding or updating a dependency, reviewing a…