Borrowing it
Nothing to install: this file belongs to AI-agents-incubator/n8n-pilot. 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/AI-agents-incubator/n8n-pilot/main/.claude/commands/analyze-local-bugs.mdgit clone --depth 1 https://github.com/AI-agents-incubator/n8n-pilotWrote 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/commands/ai-agents-incubator/n8n-pilot/analyze-local-bugs)<a href="https://agentmods.dev/commands/ai-agents-incubator/n8n-pilot/analyze-local-bugs"><img src="https://agentmods.dev/badge/commands/ai-agents-incubator/n8n-pilot/analyze-local-bugs/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/commands/ai-agents-incubator/n8n-pilot/analyze-local-bugs"><img src="https://agentmods.dev/badge/commands/ai-agents-incubator/n8n-pilot/analyze-local-bugs.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.00000 | $0.00368 |
| Opus 5 | $0.00000 | $0.00184 |
| Sonnet 5 | $0.00000 | $0.00074 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
analyze-local-bugs 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 7d 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.
What it actually says
Analyze Local Bug Reports Command
Purpose: Analyze local bug reports to find patterns and recurring issues.
Usage:
/analyze-local-bugs
Implementation
Run Pattern Analysis Script
# Check if script exists
if [ ! -f ".claude/scripts/analyze-bug-patterns.sh" ]; then
echo "⚠️ Bug pattern analyzer not found"
echo " Expected: .claude/scripts/analyze-bug-patterns.sh"
exit 1
fi
# Run analysis
bash .claude/scripts/analyze-bug-patterns.sh
What Gets Analyzed
The script analyzes all bug reports in .claude/logs/bug-reports/ and generates:
- Framework Version Distribution - Which versions have most reports
- Protocol Type Distribution - Cold Start vs Completion failures
- Most Common Errors - Top 5 error messages
- Step Failure Analysis - Which protocol steps fail most
- Recommendations - Actionable insights and fixes
Output
- Console: Visual summary with statistics and recommendations
- File: Detailed report saved to
.claude/logs/bug-analysis-TIMESTAMP.md
Notes
- Works Everywhere: Available in both framework and host projects
- Local Analysis: Analyzes only local bug reports (not GitHub Issues)
- Complementary: Use with
/analyze-bugs(GitHub Issues) for complete picture - Privacy: All data stays local, no network requests
See Also
/analyze-bugs- Analyze centralized GitHub Issues (framework project only)/bug-reporting- Manage bug reporting settings
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.
- 7d ago First seen · 60 lines · 0 tokens per session scan A 4008fee78193
analyze-local-bugs is a command published in the GitHub repository AI-agents-incubator/n8n-pilot (29 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 368 tokens. 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-09-04.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.