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 huzaifa525/claude-code-optimizer --skill fix-issuegit clone --depth 1 https://github.com/huzaifa525/claude-code-optimizerWrote 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/huzaifa525/claude-code-optimizer/fix-issue)<a href="https://agentmods.dev/skills/huzaifa525/claude-code-optimizer/fix-issue"><img src="https://agentmods.dev/badge/skills/huzaifa525/claude-code-optimizer/fix-issue/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/huzaifa525/claude-code-optimizer/fix-issue"><img src="https://agentmods.dev/badge/skills/huzaifa525/claude-code-optimizer/fix-issue.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.00028 | $0.00340 |
| Opus 5.5 | $0.00011 | $0.00136 |
| Sonnet 5.5 | $0.00006 | $0.00068 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
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 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
Fix GitHub issue #$ARGUMENTS.
Steps
-
Fetch the issue
gh issue view $ARGUMENTS -
Understand requirements — read the issue title, description, labels, and comments
-
Create a branch
git checkout -b fix/issue-$ARGUMENTS -
Find relevant code — use Grep and Glob to locate files related to the issue
-
Read the code — understand the current behavior and why it's wrong
-
Implement the fix — make the minimum changes needed
-
Write/update tests — ensure the fix is tested
-
Run tests — verify nothing is broken
[test command from CLAUDE.md or package.json] -
Commit with conventional message:
git add [specific files] git commit -m "fix: [description] (#$ARGUMENTS)" -
Show summary — what was changed, why, and what tests cover it
If issue doesn't exist
Tell the user the issue was not found.
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 · 51 lines · 28 tokens per session scan A d78479f57753
fix-issue is a skill published in the GitHub repository huzaifa525/claude-code-optimizer (10 stars, last pushed 6mo ago), licensed MIT. It adds 28 tokens to every session and 340 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
github-workflow
GitHub best practices for pull requests, code reviews, issues, Actions workflows, and repository management.
lerna
Best practices for Lerna monorepo management, versioning, and publishing.
yd-git-ship
A GitLab delivery workflow for coding agents. It defines how to create issues and branches, write commits, open and merge merge requests, and track continuous integration checks; continuous integration means automated checks run after changes are submitted.
ccc-triage
Triage a GitHub repo's open issues and PRs with the gh CLI: flag stale, unlabeled and CI-failing items, propose labels and next actions, apply labels one confirmed item at a time, or summarize the backlog. Use when a maintainer asks to triage issues or PRs, label the backlog, or wants a digest.
ccc-tasks
Track work in one markdown file, tasks/todo.md, with checkboxes, P0-P3 priorities and status marks; no database, service or sync. Use when the user asks for a todo list, wants to track personal or side-session tasks, or types $ccc-tasks.
hotfix
Single-issue workflow for quick fixes and small changes that don't need full epic tracking. Creates a branch, implements the fix, commits with issue tracking, and closes.