Borrowing it
Nothing to install: this file belongs to pankaj28843/docs-mcp-server. 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/pankaj28843/docs-mcp-server/main/.agents/skills/bug-fix/SKILL.mdgit clone --depth 1 https://github.com/pankaj28843/docs-mcp-serverWrote 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/pankaj28843/docs-mcp-server/bug-fix)<a href="https://agentmods.dev/skills/pankaj28843/docs-mcp-server/bug-fix"><img src="https://agentmods.dev/badge/skills/pankaj28843/docs-mcp-server/bug-fix/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/pankaj28843/docs-mcp-server/bug-fix"><img src="https://agentmods.dev/badge/skills/pankaj28843/docs-mcp-server/bug-fix.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.00015 | $0.00164 |
| Opus 5.5 | $0.00006 | $0.00066 |
| Sonnet 5.5 | $0.00003 | $0.00033 |
| Haiku 4.5 | $0.00002 | $0.00016 |
Grade A, and why
bug-fix 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
Steps
- Confirm scope: Identify exact entrypoints and data involved.
- Add/extend a failing test or capture the failing command output.
- Patch: Respect service-layer boundaries per Cosmic Python patterns. Use guard clauses, clear errors.
- Verify:
timeout 120 uv run pytest -m unit --no-cov -k $ARGUMENTS uv run ruff check <edited file> - Report: Summarize root cause, fix, and validation commands run.
Output
- Focused diff + brief explanation of behavioral change.
- Updated/added test demonstrating the fix.
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 · 20 lines · 15 tokens per session scan A 525c7656d1ce
bug-fix is a skill published in the GitHub repository pankaj28843/docs-mcp-server (2 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 164 once invoked, about $0.0001 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
nightly-audit-engineer-getting-started
A first-conversation guide for setting up a code-audit assistant. A code audit is a focused review of source code for defects or risky behavior, with the needed repository, scope, concerns, permissions, and schedule clarified first.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior. 4-phase root cause investigation — NO fixes without understanding the problem first.
nightly-audit-engineer-ops
A workflow for reviewing code for reproducible quality problems and recording the evidence behind each finding. It follows data through inputs, permissions, storage, asynchronous work, and recovery, then suggests the smallest authorized fix.
ha-logs
A read-only troubleshooting skill for querying Hope Agent’s local SQLite databases, which store logs, conversations, and background-job status.
ha-self-diagnosis
Self-understanding and issue reporting for Hope Agent itself. Use when the user asks how Hope Agent works internally, asks about its own source code/docs/runtime behavior, reports a bug/failure/slowness/crash, asks to diagnose logs, or asks to create/submit a GitHub issue for a bug, feature request, or improvement…
sentry-app-setup
Create and configure a Sentry internal integration so the assistant can manage issues, alerts, and releases under its own identity.