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 cyberelf/agent_skills --skill issue-fixergit clone --depth 1 https://github.com/cyberelf/agent_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/cyberelf/agent_skills/issue-fixer)<a href="https://agentmods.dev/skills/cyberelf/agent_skills/issue-fixer"><img src="https://agentmods.dev/badge/skills/cyberelf/agent_skills/issue-fixer.svg" alt="Measured on agentmods" 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.00070 | $0.00959 |
| Opus 5 | $0.00035 | $0.00479 |
| Sonnet 5 | $0.00014 | $0.00192 |
| Haiku 4.5 | $0.00007 | $0.00096 |
Grade A, and why
issue-fixer 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 7d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Fixer
Overview
This skill provides a comprehensive, systematic workflow for investigating and fixing issues with minimal impact. It ensures proper issue tracking, thorough root cause analysis, impact assessment, quality validation, and automated testing for all fixes.
When to Use This Skill
Invoke this skill when:
- User reports a bug or unexpected behavior
- Tests are failing and need investigation
- Features are broken or not working as expected
- User explicitly requests a fix for a specific issue
- Error messages or exceptions need resolution
Core Workflow
The issue-fixing process follows seven sequential phases:
- Issue Registration - Track the issue in
.issues/opening.md - Investigation - Find all related code and identify root cause
- Impact Assessment - Determine if it requires a simple fix or feature plan
- Implementation - Apply minimal, surgical changes
- Validation - Run quality checks and tests
- E2E Testing - Create/update end-to-end tests for full-stack fixes
- Finalization - Update issue status and generate summary
Quick Start Decision Tree
User reports issue
│
├─→ Is issue already tracked in .issues/opening.md?
│ ├─→ Yes: Note issue number, proceed to Investigation
│ └─→ No: Register new issue, proceed to Investigation
│
└─→ After investigation, what is the impact?
├─→ HIGH (6+ files, 200+ LOC, architecture changes, breaking changes)
│ └─→ Create feature plan, suggest handoff to speckit.plan, STOP
│
└─→ LOW/MEDIUM (1-5 files, <200 LOC, no breaking changes)
└─→ Proceed with implementation → validation → testing → finalization
Detailed Workflow
For the complete step-by-step guide covering all seven phases, refer to:
references/workflow.md - Comprehensive workflow with detailed instructions for each phase including:
- Issue registration format and procedures
- Code discovery and root cause analysis techniques
- Impact assessment criteria and decision points
- Implementation principles and patterns
- Quality validation commands for backend and frontend
- E2E testing guidelines and patterns
- Issue finalization procedures
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.
- 7d ago First seen · 126 lines · 70 tokens per session scan A e083f7e85272
issue-fixer is a skill published in the GitHub repository cyberelf/agent_skills (2 stars, last pushed 12d ago), licensed MIT. It adds 70 tokens to every session and 959 once invoked, about $0.0003 per session on Opus 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
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.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
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…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.