agentmods.dev

sentry-cli

sentry-cli is a skill for Claude Code, Codex from XyrusCode/ai-sync. It costs 49 tokens per session (5,931 once invoked), scanned C, a copy of sentry-cli, MIT.

A command-line guide for Sentry, a service that collects application errors, events, and performance traces.

In plain words
What is it for?
It helps view and list issues, inspect traces, make API calls, discover available API operations, and produce machine-readable output.
Why use it?
It gives developers a direct way to inspect and investigate reported problems without manually constructing service requests.

Skill for Claude CodeCodex

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

not rated 2repo 18d ago C scan 49 tokens copy · 94% MIT

Good fit It helps view and list issues, inspect traces, make API calls, discover available API operations, and produce machine-readable output.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/xyruscode/ai-sync/sentry-cli
View source ↗ XyrusCode/ai-sync
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 XyrusCode/ai-sync --skill sentry-cli
Clone the repo
git clone --depth 1 https://github.com/XyrusCode/ai-sync

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 sentry-cli

README.md
[![agentmods](https://agentmods.dev/badge/skills/xyruscode/ai-sync/sentry-cli/github.svg)](https://agentmods.dev/skills/xyruscode/ai-sync/sentry-cli)
Your own site
<a href="https://agentmods.dev/skills/xyruscode/ai-sync/sentry-cli"><img src="https://agentmods.dev/badge/skills/xyruscode/ai-sync/sentry-cli/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 sentry-cli

Your own site · 80×15
<a href="https://agentmods.dev/skills/xyruscode/ai-sync/sentry-cli"><img src="https://agentmods.dev/badge/skills/xyruscode/ai-sync/sentry-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,931 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 94% 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.00049 $0.05931
Opus 5.5 $0.00020 $0.02372
Sonnet 5.5 $0.00010 $0.01186
Haiku 4.5 $0.00005 $0.00593

Measured 1mo ago against content hash 6db9a5cc56e3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

sentry-cli scanned grade C with 2 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 1mo 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.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

curl https://cli.sentry.dev/install -fsS | bash

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- **`sentry api` mimics `curl`**: The `sentry api` command provides direct API access with a `curl`-like interface — `--method` for HTTP method, `--data` for request body, `--header` for custom headers. It handles authen
Origin

This is a copy

94% identical to sentry-cli — 12 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.

skills/sentry-cli/SKILL.md · 601 lines

How it starts

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

Sentry CLI Usage Guide

Help users interact with Sentry from the command line using the sentry CLI.

Agent Guidance

Best practices and operational guidance for AI coding agents using the Sentry CLI.

Key Principles

  • Just run the command — the CLI handles authentication and org/project detection automatically. Don't pre-authenticate or look up org/project before running commands. If auth is needed, the CLI prompts interactively.
  • Prefer CLI commands over raw API calls — the CLI has dedicated commands for most tasks. Reach for sentry issue view, sentry issue list, sentry trace view, etc. before constructing API calls manually or fetching external documentation.
  • Use sentry schema to explore the API — if you need to discover API endpoints, run sentry schema to browse interactively or sentry schema <resource> to search. This is faster than fetching OpenAPI specs externally.
  • Use sentry issue view <id> to investigate issues — when asked about a specific issue (e.g., CLI-G5, PROJECT-123), use sentry issue view directly.
  • Use --json for machine-readable output — pipe through jq for filtering. Human-readable output includes formatting that is hard to parse.
  • The CLI auto-detects org/project — most commands work without explicit targets by checking .sentryclirc config files, scanning for DSNs in .env files and source code, and matching directory names. Only specify <org>/<project> when the CLI reports it can't detect the target or detects the wrong one.

Design Principles

The sentry CLI follows conventions from well-known tools — if you're familiar with them, that knowledge transfers directly:

  • gh (GitHub CLI) conventions: The sentry CLI uses the same <noun> <verb> command pattern (e.g., sentry issue list, sentry org view). Flags follow gh conventions: --json for machine-readable output, --fields to select specific fields, -w/--web to open in browser, -q/--query for filtering, -n/--limit for result count.
  • sentry api mimics curl: The sentry api command provides direct API access with a curl-like interface — --method for HTTP method, --data for request body, --header for custom headers. It handles authentication automatically. If you know how to call a REST API with curl, the same patterns apply.

Read the full file on GitHub · 601 lines

Files

What ships with it

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

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. 1mo ago First seen · 601 lines · 49 tokens per session scan C 6db9a5cc56e3

Subscribe to this mod's changes

sentry-cli is a skill published in the GitHub repository XyrusCode/ai-sync (2 stars, last pushed 18d ago), licensed MIT. It adds 49 tokens to every session and 5,931 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). It is 94% identical to sentry-cli, differing in 12 lines, and is treated as a copy.

Debugging
Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

deck-retro

Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…

asheshgoplani/agent-deck · 86 tokens