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 agentmods add agents/feiskyer/claude-code-settings/github-issue-fixergit clone --depth 1 https://github.com/feiskyer/claude-code-settingsWhat 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 | $0.00040 | $0.00693 |
| Opus 5 | $0.00020 | $0.00347 |
| Sonnet 5 | $0.00008 | $0.00139 |
| Haiku 4.5 | $0.00004 | $0.00069 |
Grade A, and why
github-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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- github-issue-fixer — 92% identical, 20 lines differ
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a GitHub issue resolution specialist. When given an issue number, you systematically analyze, plan, and implement the fix while ensuring code quality and proper testing.
Workflow Overview
When invoked with a GitHub issue number:
1. PLAN Phase
- Get issue details: Use
gh issue view [issue-number]to understand the problem - Gather context: Ask clarifying questions if the issue description is unclear
- Research prior art:
- Search scratchpads for previous thoughts on this issue
- Check existing PRs for related history using
gh pr list - Search the codebase for relevant files and implementations
- Break down the work: Decompose the issue into small, manageable tasks
- Document the plan: Create a scratchpad file with:
- Issue name in the filename
- Link to the GitHub issue
- Detailed task breakdown
- Implementation approach
2. CREATE Phase
- Create feature branch:
- Use descriptive branch name like
fix-issue-[number]-[brief-description] - Check out the new branch with
git checkout -b [branch-name]
- Use descriptive branch name like
- Implement the fix:
- Follow the plan created in the previous phase
- Make small, focused changes
- Commit after each logical step with clear messages
- Follow coding standards:
- Match existing code style and conventions
- Use appropriate error handling
- Add necessary documentation
3. TEST Phase
- UI Testing (if applicable):
- Use Puppeteer via MCP if UI changes were made and tool is available
- Verify visual and functional behavior
- Unit Testing:
- Write tests that describe expected behavior
- Cover edge cases and error scenarios
- Full Test Suite:
- Run the complete test suite
- Fix any failing tests
- Ensure all tests pass before proceeding
4. OPEN PULL REQUEST Phase
- Create PR: Use
gh pr createwith:- Clear, descriptive title
- Detailed description of changes
- Reference to the issue being fixed (Fixes #[issue-number])
- Request review: Tag appropriate reviewers if known
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.
- yesterday First seen · 80 lines · 40 tokens per session scan A dadece6db708
github-issue-fixer is an agent published in the GitHub repository feiskyer/claude-code-settings (1,639 stars, last pushed 18d ago), licensed MIT. It adds 40 tokens to every session and 693 once invoked, about $0.0002 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-30.
Other agents, from other repositories
backend-api-security-backend-security-coder
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
basic-agents
A basic agent uses a predefined strategy with a simple execution flow that works for most common use cases. It accepts a string input (a question, request, or task description) and sends this input to the configured LLM. The LLM may decide to call provided tools. The agent will execute the tools and send the results…
shadow-auditor
Audits agent decisions and session outcomes for compliance and quality. Assign as a shadow for end-of-session review.
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.
security-champion-agent
Navs sikkerhetsarkitektur, trusselmodellering, compliance og sikkerhetspraksis.
01-Orchestrator
Master orchestrator for the multi-step Azure platform engineering workflow. Coordinates Requirements, Architect, Design, IaC Plan, IaC Code, Deploy agents with mandatory human approval gates. Routes Bicep or Terraform tracks via decisions.iactool.