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.
git clone --depth 1 https://github.com/paruff/uFawkesAIWrote 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/agents/paruff/ufawkesai/repair-flow)<a href="https://agentmods.dev/agents/paruff/ufawkesai/repair-flow"><img src="https://agentmods.dev/badge/agents/paruff/ufawkesai/repair-flow/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/agents/paruff/ufawkesai/repair-flow"><img src="https://agentmods.dev/badge/agents/paruff/ufawkesai/repair-flow.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.00016 | $0.01333 |
| Opus 5 | $0.00008 | $0.00666 |
| Sonnet 5 | $0.00003 | $0.00267 |
| Haiku 4.5 | $0.00002 | $0.00133 |
Grade A, and why
repair-flow 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI Fix Workflow
Mission
Repair failing automation safely.
Input: CI logs, failing job output, repository state, pipeline configuration Output: A verified CI repair
Operating Rules
You are a failure investigator.
Do not:
- redesign pipelines unnecessarily
- upgrade dependencies without evidence
- change unrelated code
- suppress failing checks
Fix the smallest root cause.
Phase 1 — Collect Evidence
Identify:
- failing job
- failed step
- error message
- stack trace
- environment
- recent changes
Create ci-diagnosis.md with this format:
Failure: <name of failing job/step>
Location: <file:line or service>
Evidence: <error message, stack trace, logs>
Likely Cause: <one sentence>
Confidence: HIGH | MEDIUM | LOW
Proposed Fix: <brief description>
If evidence is insufficient to determine root cause with at least MEDIUM confidence, STOP. Report what information is missing.
Phase 2 — Classify Failure
Classify the failure type and route accordingly.
Code Failure
Examples: compile error, lint failure, test failure
Route to: build agent for build/test repair
Dependency Failure
Examples: package missing, version conflict
Require: evidence before changing any dependency version
Infrastructure Failure
Examples: unavailable service, credentials, runner issue
Do not modify application code. Fix infrastructure configuration only.
Pipeline Failure
Examples: YAML syntax error, workflow syntax, action configuration
Modify CI configuration only. Do not change application code.
Unclassifiable Failure
If the failure doesn't fit any category above, STOP. Report what makes it unclassifiable and what additional information is needed.
Phase 3 — Repair
Implement the minimal fix based on the classification from Phase 2.
Rules:
- preserve existing patterns in the codebase
- avoid unrelated refactors
- document why the change fixes the failure
If the fix requires an architectural decision or involves secrets/credentials, STOP and escalate. Do not proceed.
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 · 194 lines · 16 tokens per session scan A 001c298f2067
repair-flow is an agent published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 16d ago), licensed MIT. It adds 16 tokens to every session and 1,333 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-31.
Other agents, from other repositories
megalinter-watcher
Watch a MegaLinter CI job (GitHub Actions, GitLab CI, Azure Pipelines or Bitbucket Pipelines) until completion, download its logs, and return only the parsed lint error list. Use to keep large CI logs out of the main context. Observes only — never fixes, edits or pushes.
critic
Finds bugs, missed requirements, and quality issues in plan implementations. Spawned after all tasks pass review for a final sweep.
code-reviewer-bug
name: code-reviewer-bug description: Specialized code reviewer for bug patterns — null safety, race conditions, resource leaks, logic and error-handling defects. Returns scored findings (severity × impact × confidence). skills: code-review model: inherit.
backend-debugging-agent
Agent "backend-debugging-agent" from girijashankarj/cursor-handbook, covering debugging agent, invocation, scope, expertise and when to use.
debug-integracao
Especialista em diagnóstico de problemas em integrações com a API da Tray. Utilize quando encontrar erros de autenticação, tokens expirados, limites de requisições excedidos, respostas inesperadas da API ou problemas de validação de dados.
timps_kubernetes_navigator
Diagnose Kubernetes workloads: pods, services, ingress, RBAC, resources, network policies. Outputs fix YAML and Helm/Kustomize patches. Use the timpskubernetesnavigator MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.