Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add yonatangross/orchestkit/plugin install orkWrote 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/yonatangross/orchestkit/errors)<a href="https://agentmods.dev/skills/yonatangross/orchestkit/errors"><img src="https://agentmods.dev/badge/skills/yonatangross/orchestkit/errors/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/skills/yonatangross/orchestkit/errors"><img src="https://agentmods.dev/badge/skills/yonatangross/orchestkit/errors.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.00070 | $0.01209 |
| Opus 5.5 | $0.00028 | $0.00484 |
| Sonnet 5.5 | $0.00014 | $0.00242 |
| Haiku 4.5 | $0.00007 | $0.00121 |
Grade B, and why
errors 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 17d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat .claude/rules/error_rules.json | jq '.rules[] | {id, signature, count: .occurrence_count}' How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Error Pattern Analysis
Analyze errors captured from Claude Code sessions to identify patterns and get actionable insights.
Quick Start
/errors # Batch analysis of historical error patterns
/debug # CC 2.1.30 real-time debug for current session
When to Use Which
| Command | Purpose | Scope |
|---|---|---|
/errors |
Batch analysis of error patterns (last 24h/7d) | Historical patterns |
/debug |
Real-time debug of current session state | Current session |
fix-issue |
Full RCA workflow for specific bug | Single issue |
CC 2.1.169+: for errors that survive
/clearand restarts,claude --safe-modeboots with every customization disabled (CLAUDE.md/plugins/skills/hooks/MCP) — the one-step test that separates "ork/hook/MCP bug" from "CC bug" before deeper analysis.
Quick Analysis
# Run batch analysis on last 24h of errors
python .claude/scripts/analyze_errors.py
# Analyze last 7 days
python .claude/scripts/analyze_errors.py --days 7
# Generate markdown report
python .claude/scripts/analyze_errors.py --report
What Gets Captured
The error collector hook captures:
- Tool name (Bash, mcp__memory__search_nodes, etc.)
- Error message (first 500 chars)
- Tool input (command/query that failed)
- Timestamp and session ID
Location: .claude/logs/errors.jsonl
Current Error Rules
Check learned patterns that trigger warnings:
cat .claude/rules/error_rules.json | jq '.rules[] | {id, signature, count: .occurrence_count}'
Files
| File | Purpose |
|---|---|
.claude/hooks/posttool/error-collector.sh |
Captures errors to JSONL |
.claude/hooks/pretool/bash/error-pattern-warner.sh |
Warns before risky commands |
.claude/scripts/analyze_errors.py |
Batch pattern analysis |
.claude/rules/error_rules.json |
Learned error patterns |
.claude/logs/errors.jsonl |
Raw error log |
Common Patterns
Connection Refused / Wrong Port
What ships with it
4 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.
- 17d ago Changed 6c0d5ce31123
- 18d ago Changed · -1 lines 199e66ad0553
- 23d ago Changed c37136ed4b61
- 26d ago Changed 4a5e00b3786c
- 1mo ago Changed 8ccee8eea896
- 1mo ago First seen · 142 lines · 70 tokens per session scan B 8fd5da4ff7d5
errors is a skill published in the GitHub repository yonatangross/orchestkit (295 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 1,209 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
resolve-publish
Commit the validated fix and follow local-only, workflow-owned, or direct PR publication.
resolve-author-fix
Find the root cause, implement a focused fix, and prove behavior with targeted tests and recordings.
resolve-review-pr
Review an existing fix PR using the audited repro and full diff, preserving branch and approval rules.
resolve-inputs
Select the Resolve mode, recover its input, check the workspace, and discover existing fixes.
cocoreview
CocoReview — structured code review with six-severity findings vocabulary, progressive disclosure architecture, and universal anti-pattern baseline. Invoked via $review [file] [--complexity] [--security] [--architecture] [--language ].
examples-qa
Verify Instructor behavior through the repository's ./examples/ suite in pass, live record, or hermetic replay mode. Use when running selected examples or the corpus, capturing and reusing recorded LLM HTTP responses, diagnosing hub results, or distinguishing real errors, assertion failures, skipped examples, and…