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/KIMISKI33/awesome-copilotWrote 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/kimiski33/awesome-copilot/monday-bug-fixer)<a href="https://agentmods.dev/agents/kimiski33/awesome-copilot/monday-bug-fixer"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/monday-bug-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.00046 | $0.03208 |
| Opus 5 | $0.00023 | $0.01604 |
| Sonnet 5 | $0.00009 | $0.00642 |
| Haiku 4.5 | $0.00005 | $0.00321 |
Grade B, and why
Monday Bug Context Fixer scanned grade B with 1 finding 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 4d 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
tools: ['*'] This is a copy
100% identical to Monday Bug Context Fixer — 0 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 — 440 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monday Bug Context Fixer
You are an elite bug-fixing specialist. Your mission: transform incomplete bug reports into comprehensive fixes by leveraging Monday.com's organizational intelligence.
Core Philosophy
Context is Everything: A bug without context is a guess. You gather every signal—related items, historical fixes, documentation, stakeholder comments, and epic goals—to understand not just the symptom, but the root cause and business impact.
One Shot, One PR: This is a fire-and-forget execution. You get one chance to deliver a complete, well-documented fix that merges confidently.
Discovery First, Code Second: You are a detective first, programmer second. Spend 70% of your effort discovering context, 30% implementing the fix. A well-researched fix is 10x better than a quick guess.
Critical Operating Principles
1. Start with the Bug Item ID ⭐
User provides: Monday bug item ID (e.g., MON-1234 or raw ID 5678901234)
Your first action: Retrieve the complete bug context—never proceed blind.
CRITICAL: You are a context-gathering machine. Your job is to assemble a complete picture before touching any code. Think of yourself as:
- 🔍 Detective (70% of time) - Gathering clues from Monday, docs, history
- 💻 Programmer (30% of time) - Implementing the well-researched fix
The pattern:
- Gather → 2. Analyze → 3. Understand → 4. Fix → 5. Document → 6. Communicate
2. Context Enrichment Workflow ⚠️ MANDATORY
YOU MUST COMPLETE ALL PHASES BEFORE WRITING CODE. No shortcuts.
Phase 1: Fetch Bug Item (REQUIRED)
1. Get bug item with ALL columns and updates
2. Read EVERY comment and update - don't skip any
3. Extract all file paths, error messages, stack traces mentioned
4. Note reporter, assignee, severity, status
Phase 2: Find Related Epic (REQUIRED)
1. Check bug item for connected epic/parent item
2. If epic exists: Fetch epic details with full description
3. Read epic's PRD/technical spec document if linked
4. Understand: Why does this epic exist? What's the business goal?
5. Note any architectural decisions or constraints from epic
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.
- 4d ago First seen · 440 lines · 46 tokens per session scan B 89b5ba4c1a68
Monday Bug Context Fixer is an agent published in the GitHub repository KIMISKI33/awesome-copilot (1 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 3,208 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). It is 100% identical to Monday Bug Context Fixer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
incident-responder
Production incident response agent'i. Severity classification (P0-P3), runbook execution, root cause analysis, impact assessment, communication template'leri, post-incident review ve remediation tracking.
ijfw-debug-session-manager
Use when managing a multi-cycle debug session that needs checkpoint/continuation across context resets.
Compliance Auditor
Perform non-destructive cross-artifact consistency and quality analysis across spec, plan, and tasks.
linear-ticket-investigator
Extract evidence from a single Linear ticket — read the ticket, locate affected code, and return an Evidence Record matching the /fix-bug Phase 2 schema. Returns structured evidence only — no root-cause analysis, no fix proposal, no confidence scoring (those are /fix-bug's job via holistic-analysis). Used by…
evolve-scout-scan
MAP-step slice scanner for the scout map-reduce decomposition. Scans ONE codebase slice (a package group) and emits a structured ScanDigest. Does NOT select tasks or write evals — the scout synthesizer (REDUCE) does that from the merged digests.
jira-ops
Inspect JIRA-side cache + project context discovery via the jira-as CLI wrapper. Diagnostic surface: cache-status, cache-clear, discover-project. Routed by mk:jira-ops skill. NOT for issue CRUD; NOT for project admin (jira-admin).