use-sentry-cli-debug

A set of instructions for using Sentry's command-line program to investigate errors, events, traces, and logs in the Vibe Remote project. Sentry is a service that collects software errors and application activity.

In plain words
What is it for?
Use it to check authentication, inspect Sentry issues or events, investigate traces and logs, and make focused command-line queries.
Why use it?
It gives debugging steps and keeps Sentry credentials out of committed project files while favoring read-only investigation.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/avibe-bot/avibe/use-sentry-cli-debug
Any agent
npx skills add avibe-bot/avibe --skill use-sentry-cli-debug
Clone the repo
git clone --depth 1 https://github.com/avibe-bot/avibe

Made for: Claude Code, Codex.

Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,168 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. Scan, not verified.
Origin original No closer match found 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 $0.00035 $0.01168
Opus 5 $0.00017 $0.00584
Sonnet 5 $0.00007 $0.00234
Haiku 4.5 $0.00003 $0.00117

Measured 3d ago against content hash 1310ed6d9631, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

use-sentry-cli-debug 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 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.

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.

curl https://cli.sentry.dev/install -fsS | bash
.agents/skills/use-sentry-cli-debug/SKILL.md · 135 lines

How it starts

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

Use Sentry CLI Debug

Use this skill when the user asks to inspect Sentry issues, events, traces, logs, or authenticated Sentry API responses from the command line while working in the Vibe Remote repository.

Core Rules

  1. Prefer sentry CLI subcommands over raw REST calls. Use sentry issue, sentry event, sentry trace, and sentry log first. Fall back to sentry api only when the dedicated command cannot expose the needed field.
  2. Do not commit credentials. Prefer sentry auth login interactive auth. If token auth is required, use a shell-scoped SENTRY_AUTH_TOKEN or another untracked local secret source. Never write tokens into tracked repo files.
  3. Keep output small. Prefer --json --fields ..., --limit ..., and jq when filtering.
  4. Stay read-only by default. Do not resolve, mute, delete, or otherwise mutate Sentry state unless the user explicitly asks.
  5. Verify CLI context before debugging. Run sentry auth status, then confirm the target org/project if auto-detection looks ambiguous.

Prerequisites

If sentry is not installed:

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

Then verify:

sentry --help
sentry auth status

Authentication options that do not require committing secrets:

# Preferred: interactive login managed by the CLI
sentry auth login

# Alternative: shell-scoped token
export SENTRY_AUTH_TOKEN=...
sentry auth login --token "$SENTRY_AUTH_TOKEN"

Never add the token to tracked files such as .env, .envrc, config/*.json, settings.json, or skill files.

Repo-Specific Context

Before querying Sentry, read vibe-remote.md for the tags and environment metadata currently attached by this repository.

Important current signals:

  • component=service for the main service
  • component=ui for the Flask UI
  • mode=<config.mode>
  • primary_platform=<config.platforms.primary>
  • deployment_environment=<resolved environment>
  • release=vibe-remote@<version>

Read the full file on GitHub · 135 lines

Files

What ships with it

1 file 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. 3d ago First seen · 135 lines · 35 tokens per session scan C 1310ed6d9631

Subscribe to this mod's changes

use-sentry-cli-debug is a skill published in the GitHub repository avibe-bot/avibe (495 stars, last pushed 3d ago), licensed MIT. It adds 35 tokens to every session and 1,168 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

vibelution-continuous-optimization-loop

Runs one evidence-driven Vibelution optimization iteration from the ROI backlog: pick one todo item, worktree isolate, implement, machine-verify, merge, update STATE. Use when the user starts /loop for project improvement, continuous optimization, or agent-dev ROI backlog work.

CCDawn/Vibelution · 65 tokens

emil-design-eng

This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.

wibus-wee/cradle-app · 35 tokens

cradle-cli

Use whenever you need to read, inspect, wait on, or mutate Cradle-owned state or workflows, including issues, delegation, sessions, awaits, CI/review waits, timed waits, Work inspection, workspaces and git inspection, Chronicle, automations, usage, observability, skills, agents, profiles, providers, preferences…

wibus-wee/cradle-app · 152 tokens

userinterface-wiki

UI/UX best practices for web interfaces. Use when reviewing animations, CSS, audio, typography, UX patterns, prefetching, or icon implementations. Covers 11 categories from animation principles to typography. Outputs file:line findings.

wibus-wee/cradle-app · 52 tokens

elysiajs

Create backend with ElysiaJS, a type-safe, high-performance framework.

wibus-wee/cradle-app · 20 tokens

transitions-dev

Production-ready CSS transitions for web apps. Use when implementing notification badges, dropdowns, modals, panel reveals, page transitions, card resizes, number pop-ins, text swaps, icon swaps, success checks, avatar group hovers, or error state shakes. Triggers on "add a transition", "animate the dropdown", "make…

wibus-wee/cradle-app · 159 tokens