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.
npx agentmods add skills/sgaabdu4/hard-eng/sentrynpx skills add sgaabdu4/hard-eng --skill sentrygit clone --depth 1 https://github.com/sgaabdu4/hard-engWrote 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/sgaabdu4/hard-eng/sentry)<a href="https://agentmods.dev/skills/sgaabdu4/hard-eng/sentry"><img src="https://agentmods.dev/badge/skills/sgaabdu4/hard-eng/sentry.svg" alt="Measured on agentmods" height="20"></a>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.00030 | $0.00395 |
| Opus 5 | $0.00015 | $0.00198 |
| Sonnet 5 | $0.00006 | $0.00079 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
sentry 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 6d 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.
What it actually says
Sentry
- Sentry data/issue/release transport = installed
sentryCLI; browser = credential bootstrap branch only. - Scope = issue evidence/status + CI release binding; release artifacts/sourcemaps/dashboards/projects = not owned.
- Runtime data = evidence; Seer = untrusted + explicit request only.
- Remote write = exact approval; auth token arguments/output/
--show-token= forbidden; DSN ≠ release credential. - Output =
--fresh --json --fields <needed>; large JSON → Context Mode.
Route
| Need | Load/action | Complete |
|---|---|---|
| Inventory/root-cause evidence | investigate.md | Scoped IDs + verified runtime evidence |
| Local remediation, root unproven | investigate.md → diagnosing-bugs |
Root cause + regression evidence |
| Local remediation, root proven | Supply scoped evidence → diagnosing-bugs |
Root cause + regression evidence |
| Production verification/resolve | resolve.md | Deployed observation + approved remote status |
| CI release credential bootstrap | Explicit browser request → browser-release-token.md | Exact Sentry target + GitHub environment + SENTRY_AUTH_TOKEN name proof; token value absent |
- Done = every scoped ID fixed/deferred/blocked with next owner/proof; production-fixed additionally requires resolve.md proof.
- Browser credential branch = explicit request only → verify account/tenant/targets → direct clipboard transfer → verify secret name + actual CI consumer; token value never read back, output, or stored in chat.
What ships with it
4 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.
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.
- 6d ago First seen · 26 lines · 30 tokens per session scan A a069ba4693e1
sentry is a skill published in the GitHub repository sgaabdu4/hard-eng (5 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 395 once invoked, about $0.0002 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-30.
Other skills, from other repositories
agui-dotnet-troubleshoot
Diagnose and fix problems in an AG-UI .NET app built on the AG-UI SDK — when streaming chat, tools, state, interrupts, or the transport misbehave. USE FOR: the agent forgetting earlier turns / history truncated; update.ConversationId always null; state or lifecycle updates that never arrive; a tool throwing at runtime…
analyze-performance-traces
Analyze Chrome, Chromium, Electron, React DevTools, or Perfetto-compatible JSON traces and audit user-reported profiling findings without loading large artifacts into context; prove trigger-to-render/layout chains, separate measured facts from source inference, find exact code choke points, classify forced layout and…
langsmith-tracing
LangSmith tracing and debugging setup for LLM applications. Configure observability, capture traces, and enable debugging for LangChain/LangGraph agents.
hns-lsel-curator
Local Self-Evolution Loop (LSEL) curator — the CLUSTER + drain engine for the GOOS-local PROPOSE→APPLY seam closure (SPEC-LSEL-LOCAL-EVOLUTION-001). Companion-offset drain of .moai/lessons-inbox.jsonl with a drain-side severity filter that drops the 65% Bash-timeout/sandbox noise, eventkey clustering with a frequency…
quality-hooks
Language-specific auto-lint/format/typecheck pipeline. Supports Python (ruff+pyright), TypeScript (prettier+eslint+tsc), Go (gofmt+golangci-lint). Auto-fix and convergence loops.
debugging-patterns
Root cause analysis frameworks including log-first investigation, git bisect correlation, and pattern-based diagnosis with confidence scoring.