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 ABilenduke/copilot-developer --skill bugfixgit clone --depth 1 https://github.com/ABilenduke/copilot-developerWrote 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/abilenduke/copilot-developer/bugfix)<a href="https://agentmods.dev/skills/abilenduke/copilot-developer/bugfix"><img src="https://agentmods.dev/badge/skills/abilenduke/copilot-developer/bugfix/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/abilenduke/copilot-developer/bugfix"><img src="https://agentmods.dev/badge/skills/abilenduke/copilot-developer/bugfix.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.00064 | $0.01666 |
| Opus 5.5 | $0.00026 | $0.00666 |
| Sonnet 5.5 | $0.00013 | $0.00333 |
| Haiku 4.5 | $0.00006 | $0.00167 |
Grade A, and why
bugfix 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.
How it starts
The opening of the file, as written. The whole thing — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bugfix Skill
Purpose
This skill handles lightweight bug fixes — problems that can be described in one document and fixed in a few hours. If the fix requires planning, designing, and roadmapping, promote it to a story instead (the brief.md explains the bug and its impact instead of a business case).
Pipeline position: Bug reported → /bugfix → bug doc + fix + tests → PR → merge
First Steps
When this skill is invoked:
- Read the template:
templates/bug-template.md - Understand the bug: Ask the user what's broken, or investigate if they've provided a description
- Determine the feature: Which feature does this bug belong to?
- If the feature exists in
docs/features/, the bug doc goes indocs/features/{feature}/bugs/ - If it's cross-cutting or unclear, ask the user
- If the feature exists in
- Assess scope: Can this be fixed in a few hours with one document?
- If yes → proceed with bugfix
- If no → suggest promoting to a story: "This looks bigger than a quick fix. Consider running
/research storyto create a proper story for it."
- Begin the fix process
Process
Phase 1: Document the Bug
- Create the bug document at
docs/features/{feature}/bugs/{YYYY-MM-DD}_{short-description}.md - Fill in using
templates/bug-template.md:- Symptoms: What the user/developer sees
- Steps to Reproduce: Numbered steps to trigger the bug
- Expected vs Actual: Clear comparison
- Severity: Critical / High / Medium / Low
Phase 2: Investigate Root Cause
- Trace the bug through the codebase
- Apply Five Whys analysis:
- Why 1: [surface cause — what directly caused the symptom]
- Why 2: [deeper cause — why that happened]
- Why 3: [root cause — the systemic issue, or as deep as meaningful]
- Continue only if the root cause isn't clear yet (not all bugs need all 5)
- Stop when you reach a systemic cause: process gap, missing validation, architectural limitation
- Document findings in the bug doc's "Root Cause — Five Whys" section
What ships with it
1 file 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.
- 1mo ago First seen · 191 lines · 64 tokens per session scan A 2d813b7c78b5
bugfix is a skill published in the GitHub repository ABilenduke/copilot-developer (4 stars, last pushed 1mo ago), licensed MIT. It adds 64 tokens to every session and 1,666 once invoked, about $0.0003 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
testing
Skill validation framework PLUS daily test-suite health and regression intelligence. Validates skill conformance (frontmatter, manifest coverage, resolver coverage). Runs the project test suite in tiered phases (unit / evals / integration / system health), classifies failures, and produces a regression-aware report.
verify
Verify that a change really works before you claim completion.
detect-static-dependencies
ACTIVATION PREREQUISITE: the request or discovered target must explicitly identify C#, .NET, .cs, or .csproj; otherwise stay dormant without invoking this skill. USE FOR: locating System.DateTime.Now/UtcNow, System.IO.File/Directory, System.Environment, HttpClient, Console, or Process usage in C#; auditing C# code for…
testing-blocks
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.
dart-downstream-fix
DART Downstream Fix: fix a DART bug reported through gz-physics or Gazebo.
test-hang-watchdog
Prevent and diagnose hanging or long-running Gradle unit tests (> 30s) in Android/Kotlin coroutines codebases. Use when running tests, when a test execution takes unexpectedly long, when background test tasks appear frozen, or when taking thread dumps (jstack) to unblock coroutine deadlocks.