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/sentrynpx skills add vmkteam/claude-plugins --skill sentrygit 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.01031 |
| Opus 5 | $0.00028 | $0.00515 |
| Sonnet 5 | $0.00011 | $0.00206 |
| Haiku 4.5 | $0.00006 | $0.00103 |
Grade A, and why
sentry 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sentry — мониторинг ошибок
Sentry (self-hosted или cloud) для мониторинга ошибок. Доступ через pcurl.
Конкретные хосты, org slug и профиль определяются при онбординге (/onboard) и хранятся в .claude/memory/project-index.md.
Подключение
Profile: @{sentry_profile}
Base URL: https://{sentry_host}/api/0
Org slug: {org}
Команды pcurl
Список проектов
pcurl @{profile} 'https://{host}/api/0/organizations/{org}/projects/' -s
Поиск issues
# За период, сортировка по частоте
pcurl @{profile} 'https://{host}/api/0/organizations/{org}/issues/?query=is:unresolved&sort=freq&statsPeriod={period}&limit=25' -s
# По проекту
pcurl @{profile} 'https://{host}/api/0/organizations/{org}/issues/?query=is:unresolved+project:{project_slug}&sort=freq&statsPeriod={period}' -s
# По endpoint/URL
pcurl @{profile} 'https://{host}/api/0/organizations/{org}/issues/?query=is:unresolved+url:{url_pattern}&sort=freq&statsPeriod={period}' -s
# По типу ошибки
pcurl @{profile} 'https://{host}/api/0/organizations/{org}/issues/?query=is:unresolved+error.type:{ErrorType}&statsPeriod={period}' -s
# Новые issues (first seen за период)
pcurl @{profile} 'https://{host}/api/0/organizations/{org}/issues/?query=is:unresolved+firstSeen:>-{period}&sort=date' -s
Детали issue
pcurl @{profile} 'https://{host}/api/0/issues/{issue_id}/' -s
pcurl @{profile} 'https://{host}/api/0/issues/{issue_id}/events/latest/' -s
pcurl @{profile} 'https://{host}/api/0/issues/{issue_id}/tags/' -s
Events (Discover)
pcurl @{profile} 'https://{host}/api/0/organizations/{org}/events/?query=event.type:error+transaction:{endpoint}&field=count()&field=title&statsPeriod={period}&sort=-count' -s
Релизы
pcurl @{profile} 'https://{host}/api/0/projects/{org}/{project_slug}/releases/?per_page=5' -s
pcurl @{profile} 'https://{host}/api/0/organizations/{org}/releases/{version}/commits/' -s
Query syntax
| Фильтр | Пример |
|---|---|
| Проект | project:{slug} |
| Статус | is:unresolved, is:resolved, is:ignored |
| Assigned | assigned:me, assigned:{username} |
| URL | url:/rpc/* |
| Тип ошибки | error.type:TimeoutError |
| Уровень | level:error, level:fatal |
| First seen | firstSeen:-1h, firstSeen:+7d |
| Times seen | times_seen:>100 |
| Текст | context deadline, invalid_grant |
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 · 97 lines · 55 tokens per session scan A 37d2eebfa1fa
sentry 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,031 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.