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 byaan-ai/byaan --skill sentrygit clone --depth 1 https://github.com/byaan-ai/byaanWrote 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/byaan-ai/byaan/sentry)<a href="https://agentmods.dev/skills/byaan-ai/byaan/sentry"><img src="https://agentmods.dev/badge/skills/byaan-ai/byaan/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/byaan-ai/byaan/sentry"><img src="https://agentmods.dev/badge/skills/byaan-ai/byaan/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.00018 | $0.01925 |
| Opus 5 | $0.00009 | $0.00962 |
| Sonnet 5 | $0.00004 | $0.00385 |
| Haiku 4.5 | $0.00002 | $0.00193 |
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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sentry API
Use the Sentry API to list and inspect error issues, query event data, and track releases. All access is read-only.
Setup Guide
1. Create an Organization Auth Token
Organization tokens are recommended over personal tokens — they are not tied to a user account, so they keep working if the creator leaves the org.
- In Sentry, go to Settings → Developer Settings → Organization Tokens
- Click "Create New Token"
- Give it a name (e.g., "Byaan")
- Copy the token (starts with
sntrys_) — it is shown only once - Paste it in Settings > Skills > Sentry in the app
Organization tokens carry a fixed read-oriented permission set (org:read, project:read, event:read, project:releases), which is exactly what this skill needs. If you need custom scopes instead, create an Internal Integration (Settings → Custom Integrations) and use its token.
2. Find Your Organization Slug
Your organization slug appears in every Sentry URL: https://sentry.io/organizations/<slug>/. Enter it in the skill settings.
3. Region / Self-hosted
The default base URL is https://sentry.io/api/0 and works for US-region SaaS organizations.
| Deployment | Base URL |
|---|---|
| SaaS (US region) | https://sentry.io/api/0 |
| SaaS (EU region) | https://de.sentry.io/api/0 |
| Self-hosted | https://your-sentry-domain/api/0 |
EU-region or self-hosted organizations need the base URL adjusted — create a custom skill pointing at the right host, reusing the endpoints documented here.
How Authentication Works
You do not need to handle authentication manually. When you call execute_skill_api(), the system automatically adds the Authorization: Bearer <token> header.
Note: Replace {organization_slug} in endpoint paths with the value from the credentials (credentials["organization_slug"]). It is not substituted automatically.
How to Call the API
execute_skill_api(
skill_name="sentry",
endpoint_path="/organizations/{organization_slug}/issues/?query=is:unresolved&statsPeriod=24h",
method="GET"
)
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.
- 11d ago First seen · 197 lines · 18 tokens per session scan A 1dbb7aba65e0
sentry is a skill published in the GitHub repository byaan-ai/byaan (95 stars, last pushed 16d ago), licensed MIT. It adds 18 tokens to every session and 1,925 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-30.
Other skills, from other repositories
debugging-executions
Debug failed or wrong-output workflow executions using executions tools. Load when the user reports execution failures, unexpected node output, empty parameter values after a successful run, or a node showing a red or failed expression error.
n8n-docs-assistant
Answers n8n product, setup, credential, node, hosting, API, and usage questions from current n8n docs. Use when the user asks how to configure, set up, troubleshoot, or understand n8n behavior, especially credential setup questions opened from the credential modal.
error-recovery-skill
Handle errors gracefully with retry strategies and fallback patterns.
observal-advanced
Recovers Observal session ingestion, manages CLI upgrades, downgrades and rollback, and performs explicit local Agent fallback when the server is unavailable. Use when the user asks to reconcile missed sessions, repair CLI version state, or continue locally after a confirmed connection or configuration failure.
fix-finding
Use when the user explicitly asks to fix and verify a validated or plausible security finding. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
compare-files
Compare two files and show differences.