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/vmkteam/claude-plugins/errorsnpx skills add vmkteam/claude-plugins --skill errorsgit clone --depth 1 https://github.com/vmkteam/claude-pluginsWhat 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.00055 | $0.01289 |
| Opus 5 | $0.00028 | $0.00645 |
| Sonnet 5 | $0.00011 | $0.00258 |
| Haiku 4.5 | $0.00006 | $0.00129 |
Grade A, and why
errors 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/errors — Дайджест ошибок
Сводка по ошибкам за период — быстрый обзор "что ломается". Не расследование (для этого /investigate).
Конкретные подключения из .claude/memory/project-index.md.
Триггер
- "какие ошибки за сегодня?"
- "дайджест ошибок за неделю"
- "что ломается в {service}?"
- "top ошибок за 24h"
Входные данные
- Период: default 24h. Варианты: 1h, 24h, 7d, 14d, 30d
- Проект: опционально (default: все)
Шаги (параллельно)
1. Sentry: top issues (скилл /sentry)
# Top по частоте
pcurl @{sentry_profile} 'https://{sentry_host}/api/0/organizations/{org}/issues/?query=is:unresolved&sort=freq&statsPeriod={period}&limit=15' -s
# Новые issues
pcurl @{sentry_profile} 'https://{sentry_host}/api/0/organizations/{org}/issues/?query=is:unresolved+firstSeen:>-{period}&sort=date&limit=10' -s
2. Prometheus: RPC и HTTP errors (скилл /prometheus)
ВАЖНО: метрика app_rpc_error_requests_total (НЕ app_rpc_request_total).
# Top RPC ошибки по методу
pcurl @{prom_profile} 'https://{prom_host}/api/v1/query' -s -G \
--data-urlencode 'query=topk(10, sum by (job, method, code) (increase(app_rpc_error_requests_total[{period}])))'
# HTTP 5xx по сервису
pcurl @{prom_profile} 'https://{prom_host}/api/v1/query' -s -G \
--data-urlencode 'query=sum by (job, code) (increase(app_http_requests_total{code=~"5.."}[{period}]))'
3. Loki: application errors (скилл /loki)
# Количество ошибок за период
pcurl @{grafana_profile} "https://{grafana_host}/api/datasources/uid/{loki_uid}/resources/query_range" -s -G \
--data-urlencode 'query=count_over_time({service_name="{service}"} | json | level="ERROR" [{period}])' \
--data-urlencode "start=$(date -v-{period_flag} +%s)000000000" \
--data-urlencode "end=$(date +%s)000000000" \
--data-urlencode 'step=3600'
4. Kibana: nginx errors (скилл /kibana, если есть)
# 5xx count за период
pcurl @{kibana_profile} 'https://{kibana_host}/api/console/proxy?path=nginx-access-*/_search&method=POST' \
-s -H 'osd-xsrf: true' -H 'Content-Type: application/json' \
-d '{"query":{"bool":{"must":[{"range":{"httpStatus":{"gte":500}}},{"range":{"@timestamp":{"gte":"now-{period}"}}}]}},"size":0,"aggs":{"by_status":{"terms":{"field":"httpStatus","size":10}}}}'
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 · 120 lines · 55 tokens per session scan A d16b7d2e72e9
errors is a skill published in the GitHub repository vmkteam/claude-plugins (7 stars, last pushed 4mo ago), licensed MIT. It adds 55 tokens to every session and 1,289 once invoked, about $0.0003 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…