Borrowing it
Nothing to install: this file belongs to avibe-bot/avibe. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/avibe-bot/avibe/master/.agents/skills/use-sentry-cli-debug/SKILL.mdgit clone --depth 1 https://github.com/avibe-bot/avibeWrote 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/avibe-bot/avibe/use-sentry-cli-debug)<a href="https://agentmods.dev/skills/avibe-bot/avibe/use-sentry-cli-debug"><img src="https://agentmods.dev/badge/skills/avibe-bot/avibe/use-sentry-cli-debug/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/avibe-bot/avibe/use-sentry-cli-debug"><img src="https://agentmods.dev/badge/skills/avibe-bot/avibe/use-sentry-cli-debug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Supply Chain · line 25 Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.Fix: Avoid downloading and executing remote scripts. Use trusted packages from PyPI/npm. If remote fetch is required, verify checksums and use HTTPS.
- high Tool Misuse · line 25 Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.Fix: Limit tool chaining depth and validate the output of each tool before passing it to the next. Require explicit user approval for multi-step chains.
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.00035 | $0.01168 |
| Opus 5.5 | $0.00014 | $0.00467 |
| Sonnet 5.5 | $0.00007 | $0.00234 |
| Haiku 4.5 | $0.00003 | $0.00117 |
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 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.
curl https://cli.sentry.dev/install -fsS | bash 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
- Prefer
sentryCLI subcommands over raw REST calls. Usesentry issue,sentry event,sentry trace, andsentry logfirst. Fall back tosentry apionly when the dedicated command cannot expose the needed field. - Do not commit credentials. Prefer
sentry auth logininteractive auth. If token auth is required, use a shell-scopedSENTRY_AUTH_TOKENor another untracked local secret source. Never write tokens into tracked repo files. - Keep output small. Prefer
--json --fields ...,--limit ..., andjqwhen filtering. - Stay read-only by default. Do not resolve, mute, delete, or otherwise mutate Sentry state unless the user explicitly asks.
- 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=servicefor the main servicecomponent=uifor the Flask UImode=<config.mode>primary_platform=<config.platforms.primary>deployment_environment=<resolved environment>release=vibe-remote@<version>
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.
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.
- 1mo ago First seen · 135 lines · 35 tokens per session scan C 1310ed6d9631
use-sentry-cli-debug is a skill published in the GitHub repository avibe-bot/avibe (633 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 1,168 once invoked, about $0.0001 per session on Opus 5.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.
Other skills, from other repositories
fix-failing-tests
Diagnose a failing test in the googleapis/mcp-toolbox repo and land a fix by reasoning from the actual error: read the failure, reproduce it, shrink it until the cause is forced into the open, then fix the cause. Use this whenever a test or CI job is red, a build breaks after a change, many packages fail at once, or a…
reproduce-bug
Reproduce a reported bug in googleapis/mcp-toolbox and decide whether it is real, delivering an evidence-backed verdict: confirmed, already fixed, misconfiguration, client-side, works as intended, not reproducible, or blocked. Use whenever a maintainer asks you to reproduce, verify, confirm, or investigate a bug…
triage-issues
Triage GitHub issues in the googleapis/mcp-toolbox repo: propose the correct labels (type / priority / product / status), check for duplicates, verify a bug has enough info to act on, and draft a triage comment. Use whenever a maintainer asks you to triage, label, categorize, prioritize, or "look at" an issue (or a…
langbot-plugin-dev
Develop, debug, and test LangBot plugins. Use when creating new LangBot plugins, fixing plugin bugs, setting up a LangBot test environment, or testing plugins via WebSocket. Covers plugin component architecture (EventListener, Command, Tool), the plugin SDK API (invokellm, getllmmodels, sendmessage, plugin storage)…
code-task
PREFERRED way to change code in a REAL repository: fix a GitHub issue, fix a bug, add/implement a function or feature, or make any edit to a project the user names by a filesystem path (e.g. /tmp/foo, /code/bar) or a git URL. Clones the repo, runs an OpenSquilla agent on the host to make the change on a task branch…
stack-trace-generic-probe
Internal helper for meta-stack-trace-investigator. Use when a stack trace language is unknown and the workflow needs language-neutral failure-contract checks, reproducer guidance, and patch targets.