Borrowing it
Nothing to install: this file belongs to trsdn/mcp-server-ppt. 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/trsdn/mcp-server-ppt/main/.github/instructions/bug-fixing-checklist.instructions.mdgit clone --depth 1 https://github.com/trsdn/mcp-server-pptWrote 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/instructions/trsdn/mcp-server-ppt/bug-fixing-checklist)<a href="https://agentmods.dev/instructions/trsdn/mcp-server-ppt/bug-fixing-checklist"><img src="https://agentmods.dev/badge/instructions/trsdn/mcp-server-ppt/bug-fixing-checklist/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/instructions/trsdn/mcp-server-ppt/bug-fixing-checklist"><img src="https://agentmods.dev/badge/instructions/trsdn/mcp-server-ppt/bug-fixing-checklist.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.00758 | $0.00758 |
| Opus 5.5 | $0.00303 | $0.00303 |
| Sonnet 5.5 | $0.00152 | $0.00152 |
| Haiku 4.5 | $0.00076 | $0.00076 |
Grade A, and why
mcp-server-ppt bug-fixing-checklist.instructions.md 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Fixing Checklist
6-step process for comprehensive bug fixes
Process
- Root Cause - Trace flow from entry point to bug, identify what's missing/wrong/ignored
- Fix Code - Minimal changes at correct layer, maintain backwards compatibility
- Add Tests - Minimum 5-8 tests: regression + edge cases + backwards compat + MCP end-to-end
- Update Docs - Minimum 3 files: tool/method docs, user docs, SuggestedNextActions, LLM prompts
- Verify Quality - Build passes (0 warnings), all tests pass, no TODOs left
- PR Description - Bug summary, root cause, fix explanation, test coverage, docs updated
Test Coverage Requirements
Core Layer (3-5 tests):
- Exact bug scenario (regression)
- Edge case variations
- Backwards compatibility validation
MCP Server Layer (2-3 tests):
- End-to-end JSON serialization flow
- Parameter passing verification
Total: 5-8 new tests minimum
Documentation Requirements
Required files (minimum 3):
- Tool/method XML documentation (
/// <summary>,/// <param>) - User-facing docs (README or component docs)
- Skill references in
skills/shared/(auto-synced to MCP prompts)
Update workflow hints:
SuggestedNextActions- reflect new capability- Error messages - include helpful hints
WorkflowHint- guide next steps
Quality Checklist
Before marking bug as fixed:
- Root cause documented
- Minimal code changes (surgical fix)
- Parameters wired through all layers
- 5-8 new tests added (Core + MCP)
- 3+ doc files updated
- Build passes (0 warnings, 0 errors)
- All tests pass (including existing)
- No TODO/FIXME markers
- Backwards compatible
- PR description comprehensive
Common Mistakes
| Mistake | Fix |
|---|---|
| Code without tests | Add tests BEFORE marking fixed |
| Code without docs | Update docs in same PR |
| Happy path only | Test edge cases, errors, backwards compat |
| Breaking changes | Make params optional, use defaults |
| Parameter ignored | Trace from tool → implementation |
| Symptoms fixed, not root cause | Understand WHY it broke |
| Incomplete PR | Document bug, fix, tests, docs updated |
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 · 110 lines · 758 tokens per session scan A b73c1ad5a24c
mcp-server-ppt bug-fixing-checklist.instructions.md is an instructions file published in the GitHub repository trsdn/mcp-server-ppt (41 stars, last pushed yesterday), licensed MIT. It adds 758 tokens to every session, about $0.0030 per session on Opus 5.5. A static security scan graded it A with 0 findings. It comes from a forked repository.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.