sentry-scan

A command that scans Sentry for production issues and attempts to fix them automatically. Sentry is a service that collects application errors and performance problems from running software.

In plain words
What is it for?
Use it to inspect Sentry-reported production issues and apply automatic fixes where supported.
Why use it?
It helps find live application problems and reduces the manual effort needed to investigate and repair them.

Command

Part of the autopilot plugin — 2 skills, 9 commands, 14 agents, 1 hook shipped together

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 commands/george11642/george-plugins/sentry-scan
Clone the repo
git clone --depth 1 https://github.com/george11642/george-plugins

Or install autopilot, the plugin that ships this one along with the rest of its 2 skills, 9 commands, 14 agents, 1 hook.

Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 368 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.00016 $0.00368
Opus 5 $0.00008 $0.00184
Sonnet 5 $0.00003 $0.00074
Haiku 4.5 $0.00002 $0.00037

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

Security

Grade A, and why

sentry-scan 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 2d 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.

plugins/autopilot/commands/sentry-scan.md · 51 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. 2d ago First seen · 51 lines · 16 tokens per session scan A d739d0c3d809

Subscribe to this mod's changes

sentry-scan is a command published in the GitHub repository george11642/george-plugins (2 stars, last pushed 5mo ago), with no licence file. It adds 16 tokens to every session and 368 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.