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 akshay5995/agent-skill-evals --skill bugfix-workflowgit clone --depth 1 https://github.com/akshay5995/agent-skill-evalsWrote 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/akshay5995/agent-skill-evals/bugfix-workflow)<a href="https://agentmods.dev/skills/akshay5995/agent-skill-evals/bugfix-workflow"><img src="https://agentmods.dev/badge/skills/akshay5995/agent-skill-evals/bugfix-workflow/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/akshay5995/agent-skill-evals/bugfix-workflow"><img src="https://agentmods.dev/badge/skills/akshay5995/agent-skill-evals/bugfix-workflow.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.00091 | $0.00314 |
| Opus 5.5 | $0.00036 | $0.00126 |
| Sonnet 5.5 | $0.00018 | $0.00063 |
| Haiku 4.5 | $0.00009 | $0.00031 |
Grade A, and why
bugfix-workflow 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.
What it actually says
bugfix-workflow
Promise: a failing repro turns into a passing repro through a minimal, explained code change.
Steps
- Read the bug report. Identify the failing observable behaviour.
- Locate or write a verifier (test, script, manual repro) that exhibits the bug. Run it and confirm it fails.
- Change the smallest amount of code that plausibly fixes the bug.
- Re-run the verifier. If it still fails, iterate. If it passes, stop.
- Explain the change in 2–3 sentences: what was wrong, what you changed, why it fixes it.
Anti-patterns
- Do not modify files unrelated to the bug.
- Do not bypass tests with
--no-verifyor by deleting assertions. - Do not push to a protected branch (e.g.
main) without explicit instruction. - Do not read or print secrets (
.env,credentials.*, files undersecrets/).
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 First seen · 37 lines · 91 tokens per session scan A 14d7a3fb8da9
bugfix-workflow is a skill published in the GitHub repository akshay5995/agent-skill-evals (3 stars, last pushed 3mo ago), licensed MIT. It adds 91 tokens to every session and 314 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-31.
Other skills, from other repositories
repro-first
Bug-fix mode that reproduces a bug in a failing test before changing any code. Entered with /repro-first.
gke-workload-scaling-troubleshooting
Diagnoses GKE HorizontalPodAutoscaler (HPA) failures — metrics showing as , FailedGetResourceMetric / FailedGetScale / FailedComputeMetricsReplicas events, missing Pod resource requests, custom/external metrics-pipeline breakage (FailedGetExternalMetric / FailedGetCustomMetric, unavailable metrics adapter…
gke-ai-troubleshooting-tpu-performance-degradation
Diagnose GKE Cloud TPU training throughput drops and step-time regressions (15%+ TPU duty-cycle drop) using ML Diagnostics Workload Monitoring (gcloud alpha mldiagnostics monitored-events / hypercomputecluster.googleapis.com/v1alpha) and 1-minute Cloud Monitoring system metrics (kubernetes.io/node/accelerator/).…
gke-ai-troubleshooting-jobset-interruption
Diagnoses GKE JobSet interruptions, restarts, and preemptions for AI/ML training workloads autonomously. Use when troubleshooting JobSet restart loops, spot VM preemptions, node readiness failures, host VM issues, or coordinator worker crashes. Don't use for general GKE cluster creation, basic workload deployment, or…
gke-node-notready
Diagnoses GKE nodes reporting NotReady or Unknown status by inspecting node conditions, events, kubelet/containerd logs, and node metrics, then proposing safe remediations. Use when nodes show NotReady, when the kubelet stops posting node status, or when workloads are evicted or stuck Pending due to node health. Don't…
bigquery-troubleshooting
Provides diagnostic workflows and step-by-step root-cause analysis procedures for actively broken, failing, or slow BigQuery jobs, execution graph and query plan stage bottlenecks, system performance issues, or unexpectedly expensive workloads. Use when interpreting symptoms, isolating bottlenecks, diagnosing cost…