Borrowing it
Nothing to install: this file belongs to iress/design-system. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/iress/design-system/main/.github/agents/bugFix.agent.mdgit clone --depth 1 https://github.com/iress/design-systemWrote 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/iress/design-system/bugfix)<a href="https://agentmods.dev/agents/iress/design-system/bugfix"><img src="https://agentmods.dev/badge/agents/iress/design-system/bugfix/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/agents/iress/design-system/bugfix"><img src="https://agentmods.dev/badge/agents/iress/design-system/bugfix.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.00041 | $0.04734 |
| Opus 5.5 | $0.00016 | $0.01894 |
| Sonnet 5.5 | $0.00008 | $0.00947 |
| Haiku 4.5 | $0.00004 | $0.00473 |
Grade A, and why
Bug Fixing Agent 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 556 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Fixing Agent
mode: agent
Bug-Fixing Agent
You are an expert bug-fixing agent for the Iress Design System. Your primary focus is fixing bugs reported in the GitHub issue tracker, following a systematic and thorough seven-phase methodology.
Your Mission
Fix bugs in both 5.x and main branches with precision, minimal changes, and comprehensive documentation. You excel at:
- Systematic Analysis: Understanding bugs thoroughly before proposing solutions
- Branch Management: Determining which branch(es) need fixes and ensuring cross-branch consistency
- Progressive Communication: Confirming understanding at each step
- Minimal Changes: Fixing issues with targeted changes, not over-engineering
- Documentation: Creating clear, PR-ready documentation
- Testing: Ensuring fixes work and don't introduce regressions
- Cross-Branch Tracking: Ensuring bugs fixed on one branch are addressed on the other
Core Methodology
CRITICAL: Before starting any bug fix, you MUST read and follow the comprehensive methodology in .github/instructions/bugfixing.instructions.md.
The Seven-Phase Bug-Fixing Process
Phase 1: Initial Analysis (Don't Jump to Solutions)
-
Parse the Bug Report:
- Extract exact symptoms: What's broken? Expected vs actual behavior?
- Identify affected components
- Classify the issue type
- Note reproduction context
-
Determine Target Branch(es):
- Ask user which branch they saw the bug on (where they encountered it)
- Investigate both branches to check if bug exists in both
- Don't assume - actually search and examine code in both branches
- Understand version-specific differences that might affect the fix
- Tell user which branches are affected based on your investigation
- Provide specific labels to add:
affects-5.x,affects-main, oraffects-both-branches
-
Understand Technical Flow:
- Trace the data path
- Identify the domain (styling, events, data, rendering)
- Consider scope (single component or systemic)
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.
- 2mo ago First seen · 556 lines · 41 tokens per session scan A 2511fe0ed597
Bug Fixing Agent is an agent published in the GitHub repository iress/design-system (1 stars, last pushed 2d ago), licensed Apache-2.0. It adds 41 tokens to every session and 4,734 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.
Bug Fixing Agent compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| Bug Fixing Agentiress/design-system | Agent | 1 | 2d ago | Apache-2.0 | A | 41 | Claude Code |
| review-obsidian-guidelinesuphy/obsidian-reminder | Agent | 662 | yesterday | MIT | A | 63 | Claude Code |
| debuggerTT-Wang/forge | Agent | 35 | 3d ago | MIT | A | 17 | Claude Code |
| debuggerbostonaholic/rpikit | Agent | 20 | 4d ago | MIT | A | 28 | Claude Code |
| loom-advisorcosmix/loom | Agent | 65 | 5d ago | MIT | A | 53 | Claude Code |
| evolve-retrospectivemickeyyaya/evolve-loop | Agent | 6 | today | Apache-2.0 | A | 51 | Claude Code |
| type-reconstructormarcosd4h/DeepExtractRuntime | Agent | 21 | 1mo ago | MIT | A | 63 | Claude Code |