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 pe-menezes/vibeflow --skill hotfixgit clone --depth 1 https://github.com/pe-menezes/vibeflowWrote 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/pe-menezes/vibeflow/hotfix)<a href="https://agentmods.dev/skills/pe-menezes/vibeflow/hotfix"><img src="https://agentmods.dev/badge/skills/pe-menezes/vibeflow/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/pe-menezes/vibeflow/hotfix"><img src="https://agentmods.dev/badge/skills/pe-menezes/vibeflow/hotfix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00102 | $0.02536 |
| Opus 5.5 | $0.00041 | $0.01014 |
| Sonnet 5.5 | $0.00020 | $0.00507 |
| Haiku 4.5 | $0.00010 | $0.00254 |
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.
Copies of this mod
2 near-identical copies found in the catalogue:
- hotfix — 94% identical, 0 lines differ
- vibeflow-hotfix — 86% identical, 63 lines differ
How it starts
The opening of the file, as written. The whole thing — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Description and examples
What it does: In one call, produces a short trace doc in .vibeflow/hotfixes/ and implements the fix, born with a regression test that failed before it. Exactly two outcomes: done or a named HALT that saves the doc and hands the next step to a human. Done carries the doc, the fix, and the regression test — red→green when the host runs tests; when it cannot, the doc declares verification: not-run and the status locks at partial. The discriminator against the other commands is evidence — an observed defect you can show, wherever it surfaced.
Examples:
hotfix— after a bug was investigated in this conversation; inherits symptom and hypothesis from the session (origin: session).hotfix login returns 500 for emails with "+"; stack trace below— symptom + evidence in the prompt, headless/CI included (origin: prompt).hotfix harness caught: audit stamps PASS on an empty diff — log attached— evidence produced by someone else: a review finding, a harness failure, a user report (origin: third-party).hotfix .vibeflow/hotfixes/2026-08-16-saldo-zero.md— resume a halted doc from where it stopped (origin: resumed).
Language
Detect the language of the user's current request or conversation. Write ALL output in that same language. Technical terms in English are acceptable regardless of the detected language. One exception: the trace doc's section names, field names, and vocabulary values stay literally in English in any output language — resuming and consolidation match them exactly.
Fix the observed defect described in the user's current request.
The one-call contract
You are a coding agent on a live defect: the evidence decides, you execute
and record. One invocation, exactly two structured outcomes — done or a
named HALT. No mandatory questions in between: a question you would need
answered becomes the HALT that motivates it, with the doc saved and the
question recorded as the human's next step. Degradation is declared, not
silent — a host that cannot run tests writes verification: not-run in the
doc and the status locks at partial.
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 Changed · -1 lines 8a81cb2effa9
- 1mo ago First seen · 226 lines · 102 tokens per session scan A 0b32f0262b45
hotfix is a skill published in the GitHub repository pe-menezes/vibeflow (32 stars, last pushed yesterday), licensed MIT. It adds 102 tokens to every session and 2,536 once invoked, about $0.0004 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-30.
Other skills, from other repositories
pair-programming
AI-assisted pair programming with multiple modes (driver/navigator/switch), real-time verification, quality monitoring, and comprehensive testing. Supports TDD, debugging, refactoring, and learning sessions. Features automatic role switching, continuous code review, security scanning, and performance optimization with…
megalinter-check
Collect MegaLinter lint errors for the current repository. Use when the user wants to know if the code passes linting, why the MegaLinter CI job fails, or before/after fixing lint errors. Two modes - watch a CI job (GitHub Actions, GitLab CI, Azure Pipelines, Bitbucket Pipelines) and parse its logs, or run MegaLinter…
polya-fix
Phase 5 of the Pólya Heuristic Coder: First-Principles Bug Remediation, Seam Tracing, Bisection Search (O(log n)), Failing Reproduction Tests, and Incubation Circuit-Breaker Gate (docs/bug-reports/{slug}-bugfix.md).
analyze-failures
Triage Katalon True Platform/TestOps test failures and file defects. Use when you need to investigate failed test results, classify each failure as product defect vs automation defect vs environment/data issue, cluster failures by common signature, find likely root cause from execution data, and optionally create…
megalinter-fix
Fix the errors reported by MegaLinter. Use after megalinter-check found errors, or when the user pastes MegaLinter/CI lint errors and wants them fixed. Applies safe fixes automatically (auto-fix linters first, then guided manual fixes using per-linter fix guides), asks the user when fixing is ambiguous, and can…
GitHub Copilot Testing Patterns
Effective patterns for using GitHub Copilot to generate, refactor, and maintain test code including prompt engineering for test generation, Copilot Chat for debugging, inline suggestions for assertions, and workspace context optimization.