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 skills add withoneai/one-agent-plugin --skill bug-snaggit clone --depth 1 https://github.com/withoneai/one-agent-pluginWrote 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/withoneai/one-agent-plugin/bug-snag)<a href="https://agentmods.dev/skills/withoneai/one-agent-plugin/bug-snag"><img src="https://agentmods.dev/badge/skills/withoneai/one-agent-plugin/bug-snag/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/withoneai/one-agent-plugin/bug-snag"><img src="https://agentmods.dev/badge/skills/withoneai/one-agent-plugin/bug-snag.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.00118 | $0.06023 |
| Opus 5 | $0.00059 | $0.03011 |
| Sonnet 5 | $0.00024 | $0.01205 |
| Haiku 4.5 | $0.00012 | $0.00602 |
Grade A, and why
bug-snag 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 5d 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.
This is a copy
72% identical to 2-chat — 294 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BugSnag through One
Bugsnag is an application stability and error monitoring platform that provides crash reporting, diagnostics, and release tracking across web, mobile, and backend applications, allowing engineering teams to detect, prioritize, and resolve software issues through integrations and real-time visibility.
One exposes BugSnag through four MCP tools. The table below carries real action ids from One's knowledge base, so for a common operation you can skip search and go straight to reading the action's parameters.
How to run an action
- Find the action in the table below, or call
search_one_platform_actionswith platformbug-snagif it is not listed. - Call
get_one_action_knowledgewith the action id. Do this every time, including for actions in this table. The table gives you the id, not the parameters. - Call
execute_one_actionwith parameters copied from that knowledge.
Never guess a parameter name, a body field, or an enum value. The knowledge has the real schema, and a guessed field is either a 400 or a silent write of the wrong thing.
Before you start
Call list_one_integrations once and confirm BugSnag is connected. If it is missing, the user has not connected it: say so and point them at https://app.withone.ai rather than reaching for raw HTTP.
Each connection carries an access field. If it reports {"policy": "methods", "methods": ["GET"]} the agent is read-only here, so plan a read-only answer instead of attempting a write that will be refused.
Before a write
Creates, updates, deletes and sends land on a real BugSnag account and cannot be recalled. State the action and the specific target in one line before the first write in a task, and let the user stop you. Reads need no confirmation.
Actions
Collaborators
| Action | Method | Path | Action id |
|---|---|---|---|
| List Collaborators for an Organization | GET | /organizations/{{organizationId}}/collaborators |
conn_mod_def::GMAID0ya54M::7ZpunyZCRrCB4Zzj7r9J5A |
| List Collaborators on a Project | GET | /projects/{{projectId}}/collaborators |
conn_mod_def::GMAIEDEbRjo::2ORY3v82SrW5346Q_fIUiw |
| List Collaborators on an Organization | GET | /organizations/{{organizationId}}/scim/v2/Users |
conn_mod_def::GMAIHpezNo8::I238-ORHT_iDPvXJuCDbXw |
| List Collaborators Using Organizations Teams | GET | /organizations/{{organizationId}}/teams/{{id}}/collaborators |
conn_mod_def::GMAIEOXEQ6Q::YsfSri_rRHORBA3SJGGfSA |
| Show a Collaborator on an Organization | GET | /organizations/{{organizationId}}/scim/v2/Users/{{id}} |
conn_mod_def::GMAIHzTirLc::Jh3q-oRySW6QOr77brcejA |
| Add a Collaborator to an Organization's Teams | POST | /organizations/{{organizationId}}/collaborators/{{id}}/team_memberships |
conn_mod_def::GMAIDTkD0cA::OsOexhodRh2pz-2ZLIn1jA |
| Bulk Invite Collaborators Using Organizations Collaborators | POST | /organizations/{{organizationId}}/collaborators/bulk_invite |
conn_mod_def::GMAIDeka_Ao::TLiO_e_ET4KnzTwuFpGWHA |
| Create a Collaborator for an Organization | POST | /organizations/{{organizationId}}/scim/v2/Users |
conn_mod_def::GMAIHonk1Ts::Uh3KtjkXQ4WXwE7rXJg1sQ |
| Delete a Collaborator for an Organization | DELETE | /organizations/{{organizationId}}/collaborators/{{id}} |
conn_mod_def::GMAIDxSVTBw::xlPeeTntTkuOPJ6JtY9Eig |
| Invite a Collaborator to an Organization | POST | /organizations/{{organizationId}}/collaborators |
conn_mod_def::GMAID7klfc0::GDzlFAjQSKmxiDKaZNUC2g |
| Remove a Collaborator from Teams in an Organization | DELETE | /organizations/{{organizationId}}/collaborators/{{id}}/team_memberships |
conn_mod_def::GMAIEWalokw::Pg27mM0vSo66a6nK906y5Q |
| Update a Collaborator for an Organization | PUT | /organizations/{{organizationId}}/scim/v2/Users/{{id}} |
conn_mod_def::GMAIH9Kx0Yc::K_N71sXbTVG-Qx1k2VdaFA |
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.
- 5d ago First seen · 231 lines · 0 tokens per session scan A 0cf785163fcd
bug-snag is a skill published in the GitHub repository withoneai/one-agent-plugin (1 stars, last pushed 19d ago), licensed MIT. It adds 118 tokens to every session and 6,023 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 72% identical to 2-chat, differing in 294 lines, and is treated as a copy.
Other skills, from other repositories
hyperpod-node-debugger
Diagnose and remediate per-node issues on a HyperPod cluster (EKS or Slurm) — a specific node is unhealthy, unresponsive, stuck, or needs replacing. Covers on-node EFA, GPU / accelerator hardware (XID, ECC, NVLink, row-remap, DCGM), Slurm node down/drained, disk and memory pressure, per-node lifecycle-script failures…
hyperpod-performance-debugger
Diagnose performance issues on Amazon SageMaker HyperPod clusters — uneven NCCL bandwidth across nodes and poor filesystem throughput. Read-only. Surfaces host-side signals (Xid, ECC, NVLink, EFA reachability, FSx saturation) and routes to the appropriate sibling skill (hyperpod-node-debugger, hyperpod-nccl…
hyperpod-cluster-debugger
Diagnose and remediate cluster-wide HyperPod (EKS or Slurm) problems — creation / deployment failures (CloudFormation, EFA health check, lifecycle scripts, capacity), EKS access, node replacement, CloudFormation nested-stack errors, post-maintenance rollback state, dangling nodes, autoscaler conflicts. Includes…
hyperpod-nccl
Diagnose NCCL failures and adjacent training-pod failures on HyperPod GPU clusters (EKS or Slurm) — training hangs, AllReduce / collective-op timeouts, EFA or libfabric errors, rendezvous failures, EFA TCP fallback, /dev/shm or memlock issues, NCCL version mismatch across pods, container OOM / exit-137 / OOMKilled…
hyperpod-slurm-debugger
Diagnostic-only skill for Slurm scheduler and node-daemon issues on Amazon SageMaker HyperPod Slurm clusters. Scope mirrors the HyperPod troubleshooting guide. Invoke when the user reports a Slurm node stuck in down/drain, "Node unexpectedly rebooted" after auto-repair, slurmd not running, jobs stuck PENDING with…
hyperpod-issue-report
Generate comprehensive issue reports from HyperPod clusters (EKS and Slurm) by collecting diagnostic logs and configurations for troubleshooting and AWS Support cases. Use when users need to collect diagnostics from HyperPod cluster nodes, generate issue reports for AWS Support, investigate node failures or…