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/bl1nk-bot/bl1nk-agents-managerWrote 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/agents/bl1nk-bot/bl1nk-agents-manager/github-issue-fixer)<a href="https://agentmods.dev/agents/bl1nk-bot/bl1nk-agents-manager/github-issue-fixer"><img src="https://agentmods.dev/badge/agents/bl1nk-bot/bl1nk-agents-manager/github-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.00029 | $0.00712 |
| Opus 5 | $0.00015 | $0.00356 |
| Sonnet 5 | $0.00006 | $0.00142 |
| Haiku 4.5 | $0.00003 | $0.00071 |
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 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.
This is a copy
92% identical to github-issue-fixer — 20 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 94 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.
- 6d ago First seen · 94 lines · 29 tokens per session scan A bad77fc255f6
github-issue-fixer is an agent published in the GitHub repository bl1nk-bot/bl1nk-agents-manager (8 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 712 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to github-issue-fixer, differing in 20 lines, and is treated as a copy.
Other agents, from other repositories
Agent Prompt: Session title and branch generation
Agent for generating succinct session titles and git branch names.
agnix-agent
Lint agent configurations using agnix CLI. Invoke agnix skill and return validation results.
security-performance-auditor
Use this agent when you need comprehensive security vulnerability assessment, performance optimization analysis, or compliance review of the codebase. Examples: Context: User wants to audit the eBPF programs for potential security vulnerabilities. user: 'Can you check our eBPF programs for any security issues?'…
git-commit-assistant
A Git commit agent that splits workspace changes into focused commits and writes Chinese Conventional Commit messages in a required dependency order.
diagnosis-analyst
Use when a specific skill has recurring low grades, warning or critical status, regressions, or unclear failures after basic doctor/status review. Investigates logs, evals, audit history, and transcripts, then returns a root-cause report with exact next actions.
ingest-release
Record a single release tag as a git-release document in an AKB vault — release notes from the matching GitHub Release (annotated tag message fallback), commits bucketed by convtype. Requires range commits pre-ingested.