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 intentic/intentic --skill sentrygit clone --depth 1 https://github.com/intentic/intenticWrote 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/intentic/intentic/sentry)<a href="https://agentmods.dev/skills/intentic/intentic/sentry"><img src="https://agentmods.dev/badge/skills/intentic/intentic/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/intentic/intentic/sentry"><img src="https://agentmods.dev/badge/skills/intentic/intentic/sentry.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00361 |
| Opus 5.5 | $0.00014 | $0.00144 |
| Sonnet 5.5 | $0.00007 | $0.00072 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
sentry scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Token in `$SENTRY_TOKEN`, base in `$SENTRY_URL`, org slug in `$SENTRY_ORG` (may be empty). Talk to `$SENTRY_URL/api/0` with `curl`. What it actually says
Sentry (connected)
Token in $SENTRY_TOKEN, base in $SENTRY_URL, org slug in $SENTRY_ORG (may be empty). Talk to $SENTRY_URL/api/0 with curl.
Header: -H "Authorization: Bearer $SENTRY_TOKEN".
- If
$SENTRY_ORGis empty, list orgs first and use a slug below:curl -s -H "Authorization: Bearer $SENTRY_TOKEN" "$SENTRY_URL/api/0/organizations/" | jq '.[] | {slug, name}' - List projects:
curl -s -H "Authorization: Bearer $SENTRY_TOKEN" "$SENTRY_URL/api/0/organizations/$SENTRY_ORG/projects/" | jq '.[] | {slug, platform}' - Unresolved issues:
curl -s -H "Authorization: Bearer $SENTRY_TOKEN" "$SENTRY_URL/api/0/organizations/$SENTRY_ORG/issues/?query=is:unresolved&limit=25" | jq '.[] | {shortId, title, count, culprit}' - Latest event for an issue:
curl -s -H "Authorization: Bearer $SENTRY_TOKEN" "$SENTRY_URL/api/0/organizations/$SENTRY_ORG/issues/<ISSUE_ID>/events/latest/" | jq '{eventID, message}'
Notes: SaaS base is https://sentry.io (or a region host like https://us.sentry.io); self-hosted uses your instance URL.
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 · 18 lines · 35 tokens per session scan A c5f70dd78e13
sentry is a skill published in the GitHub repository intentic/intentic (85 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 361 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-06.
Other skills, from other repositories
codegraph
Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, conflict detection…
stuck
Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.
structured-debugging
Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
rust-check
Run cargo check on the current Rust project to find compile errors.
troubleshoot-sandbox
Troubleshoot OpenSandbox issues by running diagnostics (logs, inspect, events, summary) via CLI or HTTP API to diagnose sandbox failures like OOM, crash, image pull errors, network problems, etc.