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 viknesh20-20/claude-code-tool-kit --skill fix-issuegit clone --depth 1 https://github.com/viknesh20-20/claude-code-tool-kitWrote 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/viknesh20-20/claude-code-tool-kit/fix-issue)<a href="https://agentmods.dev/skills/viknesh20-20/claude-code-tool-kit/fix-issue"><img src="https://agentmods.dev/badge/skills/viknesh20-20/claude-code-tool-kit/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/viknesh20-20/claude-code-tool-kit/fix-issue"><img src="https://agentmods.dev/badge/skills/viknesh20-20/claude-code-tool-kit/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.00040 | $0.00517 |
| Opus 5.5 | $0.00016 | $0.00207 |
| Sonnet 5.5 | $0.00008 | $0.00103 |
| Haiku 4.5 | $0.00004 | $0.00052 |
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
Fetch Issue Details
!gh issue view $1 2>/dev/null || echo "Usage: /fix-issue <issue-number> — requires gh CLI authenticated"
Workflow
Step 1: Understand the Issue
- Read the issue title, description, labels, and comments
- Identify: Is this a bug fix, feature request, or enhancement?
- Determine acceptance criteria — what does "done" look like?
- Note any linked issues, PRs, or referenced files
Step 2: Find Relevant Code
- Search the codebase for files/functions mentioned in the issue
- Trace the code path related to the reported behavior
- If it's a bug: try to reproduce the conditions mentally by reading the code
- Identify the minimal set of files that need to change
Step 3: Create a Branch
git checkout -b fix/issue-<number>-<short-description>
Step 4: Implement the Fix
- Make the smallest change that addresses the issue
- Follow existing code patterns and conventions
- Add or update tests to cover the fix
- Ensure no regressions in adjacent functionality
Step 5: Verify
- Run existing tests for the affected area
- Run the new tests
- Review your own diff:
git diff - Check for unintended changes
Step 6: Commit and PR
- Stage changes:
git add <files> - Commit with reference:
git commit -m "fix: <description> (#<issue-number>)" - Push:
git push -u origin <branch> - Create PR:
gh pr create --title "Fix #<number>: <title>" --body "Closes #<number>"
Rules
- Always reference the issue number in commits and PR
- Don't scope-creep — fix only what the issue describes
- If the issue is unclear, list your assumptions before implementing
- If the fix requires architectural changes, flag it and discuss before proceeding
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 · 59 lines · 40 tokens per session scan A 6afbb7bb2136
fix-issue is a skill published in the GitHub repository viknesh20-20/claude-code-tool-kit (7 stars, last pushed 5mo ago), licensed MIT. It adds 40 tokens to every session and 517 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
fix-worktree-opsx-skills-not-created
Diagnose/fix worktrees missing the generated openspec- (opsx) skills after worktreeInit. Root cause: bare npx openspec can resolve a squatted registry stub instead of the real CLI.
refactor
Safely restructure code in an isolated git worktree with test-preserved, incremental transformations.
forensics
Post-mortem investigation for failed or stuck workflows. Analyzes git history and planning artifacts.
advanced-git-rebase-bisect-worktree
Advanced git operations beyond add/commit/push. Use when rebasing, bisecting bugs, using worktrees for parallel development, recovering with reflog, managing subtrees/submodules, resolving merge conflicts, cherry-picking across branches, or working with monorepos.
feedback
Skill "feedback" from Hmbown/Codewhale, covering feedback, when to use, setup, workflow and non-goals.
reproduce-and-fix-issues
Reproduce triaged Slack bugs through a configured app-control adapter, verify existing fixes, and open a bounded draft pull request only after before-and-after proof. Use only from the configured Benny repro automation.