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/bostonorange/claude-code-framework/error-analyzenpx skills add BostonOrange/claude-code-framework --skill error-analyzegit clone --depth 1 https://github.com/BostonOrange/claude-code-frameworkWhat 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.00041 | $0.00836 |
| Opus 5 | $0.00020 | $0.00418 |
| Sonnet 5 | $0.00008 | $0.00167 |
| Haiku 4.5 | $0.00004 | $0.00084 |
Grade A, and why
error-analyze 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 2d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Error Analyze
Triage errors from your monitoring/error tracking system. Analyze with codebase context, then create tickets or dismiss.
Usage
Interactive (developer-driven)
/error-analyze
/error-analyze --type integration
/error-analyze --since 24h
CI / Unattended
/error-analyze --ci --env prod --since 24h
CI mode runs fully automated — tickets are auto-created. See CI section below.
Phase 1: Query Errors
{{ERROR_QUERY_COMMAND}}
Parse the output to extract:
- Error ID
- Error message
- Error type/category
- Source component
- Stack trace
- Timestamp
- Affected user (if available)
Phase 2: Group & Summarize
Group errors by source + type. Present triage summary:
## Error Triage Summary
Found {N} new errors across {M} sources.
| # | Source | Type | Count | Latest | Sample Error |
|---|--------|------|-------|--------|-------------|
| 1 | ComponentA | Runtime | 23 | 2026-03-05 14:30 | NullPointerException... |
| 2 | IntegrationB | HTTP | 5 | 2026-03-05 12:15 | Timeout... |
Phase 3: Analyze Each Group
For each group:
- Find source component in codebase
- Read the code around the error location
- Analyze root cause
- Suggest fix
### Group 1: ComponentA (Runtime) — 23 errors
**Pattern:** All errors are NullPointerException on record access
**Root Cause:** Missing null check before accessing optional field
**Suggested Fix:** Add null guard before field access
**Severity:** High — blocking core workflow
Phase 4: Triage Decisions
For each group:
- Create ticket → draft work item with analysis context
- Dismiss → mark as resolved with reason
- Skip → leave as new
Action: Create Ticket
{{TRACKER_CREATE_BUG}}
Update error records: {{ERROR_UPDATE_STATUS}}
Action: Dismiss
{{ERROR_DISMISS}}
Phase 5: Summary
## Triage Complete
| Group | Action | Result |
|-------|--------|--------|
| ComponentA | Ticket created | TICKET-1600 |
| IntegrationB | Dismissed | Transient timeout |
Remaining new errors: {count}
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.
- 2d ago First seen · 136 lines · 41 tokens per session scan A 69100a3f7974
error-analyze is a skill published in the GitHub repository BostonOrange/claude-code-framework (2 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 836 once invoked, about $0.0002 per session on Opus 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…