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/ginkida/rustyhand/sentrynpx skills add ginkida/rustyhand --skill sentrygit clone --depth 1 https://github.com/ginkida/rustyhandWhat 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 | $0.00010 | $0.00695 |
| Opus 5 | $0.00005 | $0.00347 |
| Sonnet 5 | $0.00002 | $0.00139 |
| Haiku 4.5 | $0.00001 | $0.00069 |
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 2d 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
100% identical to sentry — 0 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 — 53 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.
- 2d ago First seen · 53 lines · 10 tokens per session scan A 2551668159e9
sentry is a skill published in the GitHub repository ginkida/rustyhand (20 stars, last pushed 21d ago), licensed MIT. It adds 10 tokens to every session and 695 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to sentry, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
hive.browser-automation
Required before any hive-browser CLI command. The browser is driven from the terminal by running hive-browser ... --json via terminalexec — not via MCP tools. Teaches the browser lifecycle rules (the bridge attaches to the USER'S running Chrome — never kill or launch browser processes; timeouts are transport issues…
hive.linkedin-automation
Read before automating LinkedIn with browser tools. LinkedIn combines shadow DOM (#interop-outlet), strict Trusted Types CSP that silently drops innerHTML, Lexical composer, native beforeunload dialogs that hang the bridge, and aggressive spam filters — each has bitten us at least once. Verified flows for profile…
hive.worker-delegation
Concrete patterns for breaking colony work into parallel worker jobs via runplaybook — when fan-out helps, how to model the goal as a tracker table, write the worker skill, author the playbook, pilot, and let convergence retry/resume the gap.
hive.x-automation
Read before automating X / Twitter with browser tools. Verified flows for post, reply, delete, search-and-engage, plus the Draft.js compose quirks that silently disable the send button. Includes the daily-reply and job-market-reply playbooks. Requires hive.browser-automation for the underlying screenshot + coordinate…
hive.slack-notifications-setup
Set up a Slack notification channel (Sentinel) for a colony by driving the browser — reuse or create the "Hive Sentinel" Slack app from a JSON manifest, install it, capture the bot + app tokens, create/select the channel via the Slack API, and turn Sentinel on so the colony can ping the user on Slack and accept…
hive.writing-hive-skills
Author a new Agent Skill for a Hive agent that conforms to the Agent Skills specification (SKILL.md with YAML frontmatter, optional scripts/references/assets directories). Use when the user asks to create, scaffold, add, or package a new skill for a Hive agent.