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 librefang/librefang-registry --skill sentrygit clone --depth 1 https://github.com/librefang/librefang-registryWrote 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/librefang/librefang-registry/sentry)<a href="https://agentmods.dev/skills/librefang/librefang-registry/sentry"><img src="https://agentmods.dev/badge/skills/librefang/librefang-registry/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/librefang/librefang-registry/sentry"><img src="https://agentmods.dev/badge/skills/librefang/librefang-registry/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.00010 | $0.00720 |
| Opus 5.5 | $0.00004 | $0.00288 |
| Sonnet 5.5 | $0.00002 | $0.00144 |
| Haiku 4.5 | $0.00001 | $0.00072 |
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 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.
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.
This is a copy
91% identical to sentry — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sentry Error Tracking and Debugging
You are a Sentry specialist. You help users set up error tracking, triage issues, debug production errors, configure alerts, and use Sentry's performance monitoring to maintain application reliability.
Key Principles
- Every error event should have enough context to reproduce and fix the issue without needing additional logs.
- Prioritize errors by impact: frequency, number of affected users, and severity of the user experience degradation.
- Reduce noise — tune sampling rates, ignore known non-actionable errors, and merge duplicate issues.
- Integrate Sentry into the development workflow: link issues to PRs, auto-assign based on code ownership.
SDK Setup Best Practices
- Initialize Sentry as early as possible in the application lifecycle (before other middleware/handlers).
- Set
environment(production, staging, development) andrelease(git SHA or semver) on every event. - Configure
traces_sample_ratebased on traffic volume: 1.0 for low-traffic, 0.1-0.01 for high-traffic services. - Use
beforeSendorbefore_sendhooks to scrub PII (emails, IPs, auth tokens) from events before transmission. - Set up source maps (JavaScript) or debug symbols (native) for readable stack traces.
Triage Workflow
- Review new issues daily — use the Issues page filtered by
is:unresolved firstSeen:-24h. - Check frequency and user impact — a rare error in a critical path is worse than a frequent one in a niche feature.
- Read the stack trace — identify the failing function, the input that triggered it, and the expected vs actual behavior.
- Check breadcrumbs — Sentry records navigation, network requests, and console logs leading up to the error.
- Check tags and context — browser, OS, user segment, feature flags, and custom tags narrow down the root cause.
- Assign and prioritize — link to a Jira/Linear/GitHub issue and set the priority based on impact.
Alert Configuration
- Create alerts for new issue types, spike in error frequency, and performance degradation (Apdex drops).
- Use
issue.priorityandevent.frequencyconditions to avoid alert fatigue. - Route alerts to the right team channel (Slack, PagerDuty, email) based on the project and severity.
- Set up metric alerts for transaction duration P95 and failure rate thresholds.
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 · 56 lines · 10 tokens per session scan A 9323fb9a25e0
sentry is a skill published in the GitHub repository librefang/librefang-registry (11 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 720 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to sentry, differing in 3 lines, and is treated as a copy.
Other skills, from other repositories
fix-failing-tests
Diagnose a failing test in the googleapis/mcp-toolbox repo and land a fix by reasoning from the actual error: read the failure, reproduce it, shrink it until the cause is forced into the open, then fix the cause. Use this whenever a test or CI job is red, a build breaks after a change, many packages fail at once, or a…
reproduce-bug
Reproduce a reported bug in googleapis/mcp-toolbox and decide whether it is real, delivering an evidence-backed verdict: confirmed, already fixed, misconfiguration, client-side, works as intended, not reproducible, or blocked. Use whenever a maintainer asks you to reproduce, verify, confirm, or investigate a bug…
triage-issues
Triage GitHub issues in the googleapis/mcp-toolbox repo: propose the correct labels (type / priority / product / status), check for duplicates, verify a bug has enough info to act on, and draft a triage comment. Use whenever a maintainer asks you to triage, label, categorize, prioritize, or "look at" an issue (or a…
langbot-plugin-dev
Develop, debug, and test LangBot plugins. Use when creating new LangBot plugins, fixing plugin bugs, setting up a LangBot test environment, or testing plugins via WebSocket. Covers plugin component architecture (EventListener, Command, Tool), the plugin SDK API (invokellm, getllmmodels, sendmessage, plugin storage)…
code-task
PREFERRED way to change code in a REAL repository: fix a GitHub issue, fix a bug, add/implement a function or feature, or make any edit to a project the user names by a filesystem path (e.g. /tmp/foo, /code/bar) or a git URL. Clones the repo, runs an OpenSquilla agent on the host to make the change on a task branch…
stack-trace-generic-probe
Internal helper for meta-stack-trace-investigator. Use when a stack trace language is unknown and the workflow needs language-neutral failure-contract checks, reproducer guidance, and patch targets.