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 skills add mnlt/teleport --skill sentrygit clone --depth 1 https://github.com/mnlt/teleportWrote 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/mnlt/teleport/sentry)<a href="https://agentmods.dev/skills/mnlt/teleport/sentry"><img src="https://agentmods.dev/badge/skills/mnlt/teleport/sentry/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/mnlt/teleport/sentry"><img src="https://agentmods.dev/badge/skills/mnlt/teleport/sentry.svg" alt="Reviewed on agentmods" width="80" 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.00065 | $0.01630 |
| Opus 5.5 | $0.00026 | $0.00652 |
| Sonnet 5.5 | $0.00013 | $0.00326 |
| Haiku 4.5 | $0.00006 | $0.00163 |
Grade B, and why
sentry scanned grade B 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
**Do NOT suggest editing `~/.claude/settings.local.json` manually.** The `teleport-setup add-key` command handles it with backup, validation, and masked input. Stop execution until the user has run the command and restar Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sL -H "Authorization: Bearer $SENTRY_AUTH_TOKEN" \ How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sentry
Operates Sentry via REST API. Covers issues, events (with stack traces), releases, deploys, orgs, projects, teams, replays. Use when needing structured error data over UI screenshots.
Usage
- Use for: Listing unresolved prod issues, pulling stack traces for a given issue, listing releases/deploys, correlating events to commits.
- Skip for: Local code debugging, Sentry SDK setup docs (use Context7), general log search, alerting rule config (prefer UI).
Credentials check
[ -n "$SENTRY_AUTH_TOKEN" ] && echo "SENTRY_AUTH_TOKEN: PRESENT" || echo "SENTRY_AUTH_TOKEN: MISSING"
Never echo the variable directly.
If MISSING, respond to the user with EXACTLY this message (do NOT paraphrase, do NOT suggest manual JSON edits):
I need your sentry credential. Run this in another terminal — it'll open the signup page, validate format, and save it safely with masked input:
teleport-setup add-key sentryThen restart Claude Code (
/exit, thenclaude) and ask me again.
Do NOT suggest editing ~/.claude/settings.local.json manually. The teleport-setup add-key command handles it with backup, validation, and masked input. Stop execution until the user has run the command and restarted.
API
- Base URL (SaaS):
https://sentry.io/api/0(regional:us.sentry.io,de.sentry.io). - Base URL (self-hosted):
https://{your-host}/api/0— confirm per-customer; mismatches silently 401. - Auth:
Authorization: Bearer $SENTRY_AUTH_TOKEN. - Token scopes matter. Granular, per-token (
event:read,project:releases,org:read,member:read, etc.). Wrong scope → generic 401/403 with no endpoint hint. Re-mint rather than debug the header. - Pagination:
Linkheader with cursors (not?page=). Followrel="next"URL verbatim;results="true"means more pages.
Entity hierarchy
organization_slug > project_slug > issue_id > event_id. Issues live under org, not project (common 404 source). Slugs are lowercase-hyphen; display names never work.
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 · 107 lines · 65 tokens per session scan B 8ef1aa4cce2f
sentry is a skill published in the GitHub repository mnlt/teleport (8 stars, last pushed 5mo ago), licensed MIT. It adds 65 tokens to every session and 1,630 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
triage
Diagnose and fix broken MCP servers in mcptoon — doctor, health, per-server probes, and the common failure playbook.
atomic-debug
Hypothesis-driven debugging skill. Use when a bug, test failure, crash, or unexpected behavior is reported. Auto-trigger on error pastes or "broken/doesn't work/failing" language. Explicit invocation: /atomic-debug. Output: symptom statement → hypothesis table → cheapest test first → root cause. No symptom-patching.…
sipcode-regress
Check the user's own local Claude Code and Codex logs for regressions after an update (prompt-cache misses, 5-minute cache TTL, uncached context, hourly cache rebuilds, Codex usage limit draining faster per token) and pin each one to the version that introduced it, using the Sipcode CLI. Use when the user asks whether…
ralphctl-debugging-and-error-recovery
Systematic root-cause debugging. Use when tests fail, builds break, something that worked before broke, or behaviour does not match expectations — when you need to figure out what broke and why. Follow stop-the-line → reproduce → localize → reduce → root-cause → guard-with-regression-test → verify, not guessing; the…
ralphctl-code-simplification
Behaviour-preserving simplification of existing code — understand why the code exists before changing it, then reduce nesting, unclear names, duplication, dead code, and needless indirection one step at a time with the existing tests unchanged and green after each. Use when a task asks to refactor or clean up working…
system-health
Suggest whether the machine needs a DISK or MEMORY cleanup — and catch the case where Heimdall ITSELF is the hog (runaway orphaned python from the presence keeper). Use when the machine is slow / swapping / laggy, disk or "System Data" is full, memory is exhausted, at the start of a long session, or when the user asks…