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/dapi/claude-code-marketplace/bugsnagnpx skills add dapi/claude-code-marketplace --skill bugsnaggit clone --depth 1 https://github.com/dapi/claude-code-marketplaceWrote 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/dapi/claude-code-marketplace/bugsnag)<a href="https://agentmods.dev/skills/dapi/claude-code-marketplace/bugsnag"><img src="https://agentmods.dev/badge/skills/dapi/claude-code-marketplace/bugsnag.svg" alt="Measured on agentmods" 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 | $0.00565 | $0.01845 |
| Opus 5 | $0.00282 | $0.00923 |
| Sonnet 5 | $0.00113 | $0.00369 |
| Haiku 4.5 | $0.00056 | $0.00185 |
Grade A, and why
bugsnag 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 3d 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill для интеграции с Bugsnag API, позволяющий просматривать и управлять ошибками в проекте.
⚠️ PATH RESOLUTION: Этот skill использует Ruby скрипты из своей директории.
НИКОГДА не вызывай ./bugsnag.rb из текущей рабочей директории пользователя.
ПРАВИЛЬНО: find ~ -name "bugsnag.rb" -type f | head -1 | xargs dirname → получим путь к skill
НЕПРАВИЛЬНО: ./bugsnag.rb из текущей директории → ошибка "no such file or directory"
ВАЖНО: Используй ТОЛЬКО команды, описанные в этом файле. НЕ анализируй код bugsnag.rb - следуй документации ниже.
Вызывает скрипт ./bugsnag.rb находающийся в каталого этого skill с целью выполнить пользовательский запрос.
Path Resolution для Claude
КРИТИЧЕСКИ ВАЖНО: При выполнении команд НЕ ИСПОЛЬЗУЙ ./bugsnag.rb из текущей директории пользователя.
Всегда определяй директорию где находится skill и выполняй скрипт оттуда.
Проблема
Когда пользователь говорит "покажи ошибки из bugsnag", выполнение ./bugsnag.rb из текущей директории не работает.
Решение
- Определи директорию skill
- Перейди в неё
- Выполни скрипт
Команда для Claude: Используй bash -c "cd [path_to_skill] && ./bugsnag.rb [args]"
Где [path_to_skill] - это путь к директории skill. Определи его с помощью:
find ~/.claude -name "bugsnag.rb" -type f(если установлен)- или используй
pwdесли ты уже в директории skill - или попробуй стандартные пути установки плагинов
Возможности
- Управление организациями - Просмотр списка доступных организаций в Bugsnag
- Управление проектами - Просмотр списка доступных проектов
- Просмотр текущих ошибок - Получение списка активных ошибок из Bugsnag
- Детальный контекст ошибки - Просмотр полной информации об ошибке включая stack trace
- ✅ Управление статусами - Пометка ошибок как выполненные (resolved)
- Безопасная авторизация - Использование API ключей из переменных окружения
Команды bugsnag.rb
Обзор
organizations/orgs/организации- Список всех организацийprojects/проекты- Список всех проектов
What ships with it
6 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.
- 3d ago First seen · 170 lines · 565 tokens per session scan A 65743c04993b
bugsnag is a skill published in the GitHub repository dapi/claude-code-marketplace (16 stars, last pushed 4mo ago), licensed MIT. It adds 565 tokens to every session and 1,845 once invoked, about $0.0028 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-30.
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…