Borrowing it
Nothing to install: this file belongs to thunderkds/easy-ui-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/thunderkds/easy-ui-mcp/main/.claude/skills/bugfix/SKILL.mdgit clone --depth 1 https://github.com/thunderkds/easy-ui-mcpWrote 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/thunderkds/easy-ui-mcp/bugfix)<a href="https://agentmods.dev/skills/thunderkds/easy-ui-mcp/bugfix"><img src="https://agentmods.dev/badge/skills/thunderkds/easy-ui-mcp/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/thunderkds/easy-ui-mcp/bugfix"><img src="https://agentmods.dev/badge/skills/thunderkds/easy-ui-mcp/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.00000 | $0.02413 |
| Opus 5.5 | $0.00000 | $0.00965 |
| Sonnet 5.5 | $0.00000 | $0.00483 |
| Haiku 4.5 | $0.00000 | $0.00241 |
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 yesterday.
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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: Bug Fix Orchestrator
Triage incoming defects and orient the investigation so the team shares one verified mental model before any code is touched — because a wrong overview produces a wrong fix with no way back.
Karpathy Operational Commands
- Ask vs. Guess: Never fill an unknown field with a guess. If the symptom, expected behaviour, or context is ambiguous, ask. One question at a time — do not batch a wall of questions.
- Think Before Coding: The mental model statement in Step 2 must be confirmed by the user before the TASK_GUIDE is written. An unconfirmed model is a liability, not a starting point.
- Surgical Changes: The fix touches only the code path the diagnosis implicates. No opportunistic cleanup.
Step 1 — Surface intake
Collect the minimum signal needed to begin investigation. Ask for any item that is missing or vague:
| Field | What to ask |
|---|---|
| Symptom | What is the observed behaviour? What did you expect instead? |
| Trigger | What are the exact steps or inputs that cause it? |
| Severity | P0 (down / data loss), P1 (blocking), P2 (degraded / workaround exists) |
Do not ask about affected files or root cause yet — that is the job of Step 2.
Completion criterion: symptom (observed vs expected) is concrete and unambiguous; trigger is specific enough to attempt reproduction; severity is set.
Step 2 — Orient: build and confirm the mental model
This step is a hard gate. Do not write the TASK_GUIDE until the user confirms the mental model.
A wrong mental model at this point produces a wrong fix with no way back. Invest time here.
2a — Investigate context
Before forming any theory, read the relevant code and history:
- Read the files or modules the symptom points to.
- Run
git log --oneline -10 -- <affected paths>— check for recent changes that could have introduced the regression. - Check
memory/decisions.mdandmemory/learnings.mdfor prior decisions or known gotchas in this area. - Ask the user: "When did this last work correctly?" and "Has anything changed recently in this area (deploy, config, dependency update)?"
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.
- yesterday First seen · 206 lines · 0 tokens per session scan A 2c500f17cea7
bugfix is a skill published in the GitHub repository thunderkds/easy-ui-mcp (1 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,413 tokens. 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-10-30.
Other skills, from other repositories
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
ci-fixer
CI failures - read error, minimal fix, verify.
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
diagnosing-missing-recordings
Diagnoses why a session recording is missing or was not captured. Use when a user asks why a session has no replay, why recordings aren't appearing, or wants to troubleshoot session replay capture issues for a specific session ID or across their project. Covers SDK diagnostic signals, project settings, sampling…