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.
git clone --depth 1 https://github.com/akiojin/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/commands/akiojin/skills/gh-fix-issue)<a href="https://agentmods.dev/commands/akiojin/skills/gh-fix-issue"><img src="https://agentmods.dev/badge/commands/akiojin/skills/gh-fix-issue.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.00078 | $0.00471 |
| Opus 5 | $0.00039 | $0.00235 |
| Sonnet 5 | $0.00016 | $0.00094 |
| Haiku 4.5 | $0.00008 | $0.00047 |
Grade A, and why
gh-fix-issue 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 6d 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
GitHub Issue Fix Command
Use this command to analyze a GitHub Issue and propose a fix plan.
Usage
/github:gh-fix-issue [issue-number|issue-url|optional context]
Steps
- Load
github/skills/gh-fix-issue/SKILL.mdand follow the workflow. - Run the inspection script to gather issue data and extract context.
- Search the codebase for relevant files and definitions.
- Produce an Issue Analysis Report.
- Propose fixes and apply them after user approval.
Proactive Trigger Examples
Examples
/github:gh-fix-issue 42
/github:gh-fix-issue https://github.com/org/repo/issues/123
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.
- 6d ago First seen · 62 lines · 78 tokens per session scan A 8304d34cfc18
gh-fix-issue is a command published in the GitHub repository akiojin/skills (8 stars, last pushed 6mo ago), licensed MIT. It adds 78 tokens to every session and 471 once invoked, about $0.0004 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 commands, from other repositories
fix-issues
Diagnose, reproduce, then fix reproducible open GitHub issues in parallel: one clean worktree/issue; symlink build artifacts to avoid rebuilds.
unbloat
Remove dead code, duplicate files, and unused dependencies with user approval at each step. Backs up before deleting.
payload-revert
Stage reverts for high-confidence payload candidates identified by payload-analysis.
bug-fix
Streamlines bug fixing by creating a GitHub issue first, then a feature branch for implementing and thoroughly testing the solution before merging.
CLAUDE
When debugging TUI commands like wt switch (interactive picker), use the tmux-cli skill (preferred) or MCP's node-terminal tools to test interactively.
fix-issue
Analyze and fix the GitHub issue: $ARGUMENTS.