bugsnag-automation

bugsnag-automation is a skill for Claude Code, Codex from nevergoodstudy-hub/wechat-article-summarizer. It costs 28 tokens per session (737 once invoked), scanned A, a copy of ably-automation, MIT.

An integration for automating Bugsnag operations through Rube MCP. Bugsnag is a service that records software errors and helps teams investigate them.

In plain words
What is it for?
Use it to discover and run supported Bugsnag workflows for investigating application errors.
Why use it?
It can reduce manual work when retrieving or managing error information from Bugsnag. The exact supported actions depend on the connected tools.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to discover and run supported Bugsnag workflows for investigating application errors.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nevergoodstudy-hub/wechat-article-summarizer/bugsnag-automation
Install

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.

Any agent
npx skills add nevergoodstudy-hub/wechat-article-summarizer --skill bugsnag-automation
Clone the repo
git clone --depth 1 https://github.com/nevergoodstudy-hub/wechat-article-summarizer

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for bugsnag-automation

README.md
[![agentmods](https://agentmods.dev/badge/skills/nevergoodstudy-hub/wechat-article-summarizer/bugsnag-automation/github.svg)](https://agentmods.dev/skills/nevergoodstudy-hub/wechat-article-summarizer/bugsnag-automation)
Your own site
<a href="https://agentmods.dev/skills/nevergoodstudy-hub/wechat-article-summarizer/bugsnag-automation"><img src="https://agentmods.dev/badge/skills/nevergoodstudy-hub/wechat-article-summarizer/bugsnag-automation/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.

agentmods 80×15 button for bugsnag-automation

Your own site · 80×15
<a href="https://agentmods.dev/skills/nevergoodstudy-hub/wechat-article-summarizer/bugsnag-automation"><img src="https://agentmods.dev/badge/skills/nevergoodstudy-hub/wechat-article-summarizer/bugsnag-automation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 737 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 84% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00028 $0.00737
Opus 5 $0.00014 $0.00368
Sonnet 5 $0.00006 $0.00147
Haiku 4.5 $0.00003 $0.00074

Measured 7d ago against content hash c00d950fd599, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

bugsnag-automation 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 7d 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.

Origin

This is a copy

84% identical to ably-automation — 24 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.

.warp/skills/bugsnag-automation/SKILL.md · 92 lines

How it starts

The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Bugsnag Automation via Rube MCP

Automate Bugsnag operations through Composio's Bugsnag toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/bugsnag

Prerequisites

  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Bugsnag connection via RUBE_MANAGE_CONNECTIONS with toolkit bugsnag
  • Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

  1. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  2. Call RUBE_MANAGE_CONNECTIONS with toolkit bugsnag
  3. If connection is not ACTIVE, follow the returned auth link to complete setup
  4. Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Bugsnag operations", known_fields: ""}]
session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Bugsnag task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["bugsnag"]
session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL
tools: [{
  tool_slug: "TOOL_SLUG_FROM_SEARCH",
  arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"

Known Pitfalls

  • Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  • Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
  • Schema compliance: Use exact field names and types from the search results
  • Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
  • Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
  • Pagination: Check responses for pagination tokens and continue fetching until complete

Read the full file on GitHub · 92 lines

Changes

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.

  1. 7d ago First seen · 92 lines · 28 tokens per session scan A c00d950fd599

Subscribe to this mod's changes

bugsnag-automation is a skill published in the GitHub repository nevergoodstudy-hub/wechat-article-summarizer (5 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 737 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to ably-automation, differing in 24 lines, and is treated as a copy.

Related

Other skills, from other repositories

wiki-lint

Run a deterministic, read-only health check on an Obsidian wiki. Use for lint, vault health check, audit wiki health, find orphans, find dead links, frontmatter audit, provenance audit, or wiki audit. Reports graph, link, frontmatter, provenance-ledger, empty-section, and stale-index findings; it does not reason…

AgriciDaniel/claude-obsidian · 79 tokens

debug-issue

Systematically debug issues using graph-powered code navigation.

tirth8205/code-review-graph · 13 tokens

code-understand

Build a ranked, citation-backed focus map of a codebase — the files and symbols an architecture actually hangs on — using CodeGraph when available and a dependency-free builtin (regex AST extraction + rg cross-file references) otherwise. Use this any time you (the coding agent) need to orient in an unfamiliar or large…

Ar9av/obsidian-wiki · 175 tokens

api-errors

McpError constructor, JsonRpcErrorCode reference, and error handling patterns for @cyanheads/mcp-ts-core. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.

cyanheads/obsidian-mcp-server · 54 tokens

report-issue-framework

File a bug or feature request against @cyanheads/mcp-ts-core when you hit a framework issue. Use when a builder, utility, context method, or config behaves contrary to the documented API — not for server-specific application bugs.

cyanheads/obsidian-mcp-server · 52 tokens

report-issue-local

File a bug or feature request against this MCP server's own repo. Use for server-specific issues — tool logic, service integrations, config problems, or domain bugs that aren't caused by the framework.

cyanheads/obsidian-mcp-server · 44 tokens