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 rfxlamia/pocketto --skill hotfixgit clone --depth 1 https://github.com/rfxlamia/pockettoWrote 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/rfxlamia/pocketto/hotfix)<a href="https://agentmods.dev/skills/rfxlamia/pocketto/hotfix"><img src="https://agentmods.dev/badge/skills/rfxlamia/pocketto/hotfix.svg" alt="Measured on agentmods" 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.00066 | $0.01022 |
| Opus 5 | $0.00033 | $0.00511 |
| Sonnet 5 | $0.00013 | $0.00204 |
| Haiku 4.5 | $0.00007 | $0.00102 |
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 8d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hotfix
Fast, accurate iteration. Not cowboy coding. Not full superpowers ceremony.
Use this when: Small-to-medium changes where brainstorm → spec → plan → review is overkill.
Use pocket-grinding instead when: New system, architectural decision, unclear/contested requirements, or work spanning many files/phases. (A small, clearly-specified feature addition — e.g. a zoom button or CSV export — stays here in hotfix; "it's a feature" alone is not a reason to escalate.)
The 5-Step Flow
Step 1: Capture intent Restate the goal in 1-2 sentences. Surface ambiguity now, not after coding. If the requirement is unclear after 1 clarifying question, escalate to superpowers/brainstorming.
Step 2: Write brief plan
3-5 bullets covering: what changes, where, how, and test approach.
Load references/plan-format.md to know what a valid plan looks like.
Takes 30 seconds. Not a spec. Not a doc. Just bullets.
Step 3: Dispatch subagent reviewer
Dispatch a general-purpose subagent to review the brief plan using validate-plan.
Load references/reviewer-dispatch.md for the exact dispatch template.
This is the anti-self-confidence gate. You do not review your own plan.
Step 4: Fix issues from review
- CRITICAL → fix before implementing. Non-negotiable.
- WARNING → fix unless you have explicit reason not to.
- INFO → apply if easy.
- Max 3 review iterations → if still CRITICAL after 3 passes, surface to user.
Step 5: Implement Execute the reviewed plan. Nothing beyond what the plan says.
Hard Gates
This applies to EVERY task regardless of size, urgency, or who asked. "Simple" changes skip the gate most often and cause the most silent bugs.
Why the Subagent — Not You
You wrote the plan. You are confident in it. That confidence is the problem.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 102 lines · 66 tokens per session scan A 414bb6a12a86
hotfix is a skill published in the GitHub repository rfxlamia/pocketto (5 stars, last pushed 15d ago), licensed MIT. It adds 66 tokens to every session and 1,022 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-31.
Other skills, from other repositories
independent-review-loop
Independent review loop run before delivery in code work. An independent reviewer (Codex, or fresh Codex-style subagents) reads the whole PR against the approved outcome; the lead fixes in-scope functional findings and re-reviews until none remain. Its differentiator is independence and exhaustiveness — a reviewer…
writing-style
Structural pattern analysis for writing-mode review. Performs paragraph-level decomposition and pattern aggregation. Invoked by the team lead during editorial review.
code-mode
Code mode operational spec for the team lead. Returns lead identity, facilitator identity, mode-specific rules, suggest-members guidance, and phase arc for code-mode teams.
writing-mode
Writing mode operational spec for the team lead. Returns lead identity, facilitator identity, ownership boundaries, editorial baseline, suggest-members guidance, and phase arc for writing-mode teams.
triage-mode
Triage mode operational spec for the team lead. Returns lead identity, facilitator identity, mode-specific rules, suggest-members guidance, and phase arc for triage teams that diagnose an issue without changing it.
gate-presentation
Returns the frozen gate constants — question, header, option labels and descriptions, digest field-list, and preview content — for every catalog gate. Invoked by the team lead fresh on arrival at each gate and on pulse re-emissions, in the same turn as the render. The transport contract, three renders, partition rule…