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 skills/event4u-app/agent-config/bug-analyzernpx skills add event4u-app/agent-config --skill bug-analyzergit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/event4u-app/agent-config/bug-analyzer)<a href="https://agentmods.dev/skills/event4u-app/agent-config/bug-analyzer"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/bug-analyzer.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 | $0.00039 | $0.03139 |
| Opus 5 | $0.00019 | $0.01570 |
| Sonnet 5 | $0.00008 | $0.00628 |
| Haiku 4.5 | $0.00004 | $0.00314 |
Grade A, and why
bug-analyzer scanned grade A 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Backend bug**: reproduce with `curl` against the failing route (or an `actingAs()` HTTP test) before and after the fix; assert the new response shape with `assertJsonPath`. How it starts
The opening of the file, as written. The whole thing — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bug-analyzer
When to use
Reactive mode: User reports a bug, shares a Sentry issue, or asks to investigate an error. Proactive mode: User asks to audit code for hidden bugs, edge cases, or risky patterns.
Do NOT use when:
- Feature development — route to
feature-planning - Code style or refactoring — route to
code-refactoring - Performance issues — route to
performance-analysis - Security vulnerabilities — route to
security-audit - You need to trace how one data element flows through the code — route to
data-flow-mapper - You need to enumerate every call site / consumer affected by a planned fix —
route to
blast-radius-analyzer
Input sources
Bugs can come from multiple sources — gather as many as available:
| Source | What it provides |
|---|---|
| Branch name | Auto-detected ticket ID (e.g., fix/DEV-1234/...) |
| Jira ticket | Description, acceptance criteria, comments, priority |
| Sentry issue URL | Stacktrace, affected users/environments, frequency, tags |
| Sentry event ID | Specific occurrence with full context |
| Error message | String to search in codebase |
| User description | Reproduction steps, expected vs. actual behavior |
Branch ticket detection
Always check the current branch for ticket IDs:
git branch --show-current
Pattern matching:
fix/DEV-1234/description→ extractDEV-1234fix/PROJ-567-some-bug→ extractPROJ-567hotfix/DEV-999→ extractDEV-999- Regex:
[A-Z]+-[0-9]+
If found, auto-fetch the ticket and confirm with the user.
The Iron Law
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
If you haven't completed Phase 1, you cannot propose fixes. Random fixes waste time and create new bugs. Quick patches mask underlying issues.
Red flags — STOP immediately
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 306 lines · 39 tokens per session scan A 4e17803a44f5
bug-analyzer is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 3,139 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
save-progress
Save current project task progress to local task state file for cross-session continuity. Use when the user asks to save progress, uses an equivalent localized trigger phrase, the session is interrupted, or the user wants to resume work later. Writes to .claude/project-task-state.json so next session can load it via…
meta-theory
MetaKim executable governance dispatcher. It classifies the run, loads only needed references, preserves foundational capabilities and runtime-native abilities, routes owner + weapon + dependency + runtime + OS + verification, and closes only with evidence, intent acceptance, and writeback decision.
same-set-reusable-flow-for-project-file-inventor
Reusable MetaKim file inventory classification flow. It helps separate durable sources, generated evidence, runtime mirrors, temporary state, and risky unknowns before cleanup or commit.
starreel-drama-production
Operating skill for any AI agent driving the StarReel short-drama production pipeline (script → rewrite → extract → portraits + sheets → storyboards → frames → video → voiceover → final cut) over MCP or REST. Covers the ordered workflow, the entry-point decision table (which channel each kind of customer material…
seedance-20
Generate and direct cinematic AI videos with Seedance 2.0 (ByteDance/Dreamina/Jimeng). Covers text-to-video, image-to-video, video-to-video, and reference-to-video workflows with @Tag asset references, multi-character scenes, audio design, and post-processing. Use when making AI video, writing Seedance prompts…
browse-and-evaluate
Use when exploring the ai-agent-skills catalog to find, compare, and evaluate skills before installing. Always use --fields to limit output size and --dry-run before committing to an install.