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 cyfung1031/skills --skill github-issue-fix-plannergit clone --depth 1 https://github.com/cyfung1031/skillsWrote 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/cyfung1031/skills/github-issue-fix-planner)<a href="https://agentmods.dev/skills/cyfung1031/skills/github-issue-fix-planner"><img src="https://agentmods.dev/badge/skills/cyfung1031/skills/github-issue-fix-planner/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/cyfung1031/skills/github-issue-fix-planner"><img src="https://agentmods.dev/badge/skills/cyfung1031/skills/github-issue-fix-planner.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.00060 | $0.03388 |
| Opus 5.5 | $0.00024 | $0.01355 |
| Sonnet 5.5 | $0.00012 | $0.00678 |
| Haiku 4.5 | $0.00006 | $0.00339 |
Grade A, and why
github-issue-fix-planner 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 2mo 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 — 982 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Convert a GitHub issue and a related source-code repository into a practical, review-ready engineering proposal.
The output should help a contributor or maintainer move from:
A user-visible bug report
to:
A likely root cause, concrete source-code fix direction, test plan, commit message, and PR body
This skill is designed for generic GitHub issues across frontend, backend, CLI, browser, library, build, packaging, integration, and platform-specific projects.
1. Inputs
Required
Issue URL:
Source repository URL:
Optional but useful
Related issues:
Related PRs:
Affected version:
Known working version:
Known broken version:
Operating system:
Runtime / browser / framework:
Logs:
Stack trace:
Screenshots:
Minimal reproduction:
Local reproduction notes:
Expected behavior:
Actual behavior:
Known workaround:
User’s intended target repository:
Important distinction
Sometimes the issue is filed in one repository, but the real fix belongs in another.
Always distinguish:
Reporter repository:
Repository where symptom is observed:
Fix target repository:
Repository where source-code change should likely be made:
Downstream workaround:
A local mitigation in the affected app/project:
Upstream/root fix:
A fix in the component that actually owns the failing behavior:
2. Core Principle
Do not jump from symptom directly to patch.
First find the failure boundary.
The failure boundary is the earliest point where the system stops behaving as expected.
Ask:
What action starts the flow?
Which code receives it?
Which rule/config/request/event/job is created?
Does registration succeed?
Does matching succeed?
Does validation succeed?
Does the selected action execute?
Does the result commit, render, persist, or return?
Where does expected behavior first become broken behavior?
The best code fix usually belongs at that boundary.
3. Investigation Workflow
Step 1: Read the issue fully
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.
- 2mo ago First seen · 982 lines · 60 tokens per session scan A 4e577ad3322b
github-issue-fix-planner is a skill published in the GitHub repository cyfung1031/skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 60 tokens to every session and 3,388 once invoked, about $0.0002 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
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…