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/arvo-ai/aurora/sentrynpx skills add Arvo-AI/aurora --skill sentrygit clone --depth 1 https://github.com/Arvo-AI/auroraWrote 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/arvo-ai/aurora/sentry)<a href="https://agentmods.dev/skills/arvo-ai/aurora/sentry"><img src="https://agentmods.dev/badge/skills/arvo-ai/aurora/sentry.svg" alt="Measured on agentmods" 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 | $0.00028 | $0.01214 |
| Opus 5 | $0.00014 | $0.00607 |
| Sonnet 5 | $0.00006 | $0.00243 |
| Haiku 4.5 | $0.00003 | $0.00121 |
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 5d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sentry Integration
Overview
Sentry error tracking integration for querying issues, events, and project data during Root Cause Analysis. Sentry is a REMOTE service. Use ONLY the query_sentry API tool. All data is accessed via the Sentry web API with the resource_type parameter.
Instructions
Tool Usage
query_sentry(resource_type=TYPE, query=QUERY, stats_period=PERIOD, project=PROJECT, limit=N)
Resource Types
'issues'-- Search issues.queryis a Sentry search expression (e.g.is:unresolved level:error)'issue_detail'-- Get metadata for one issue.queryis the numeric Sentry issue ID'issue_event'-- Get the latest event for an issue with full stacktrace + breadcrumbs + tags.queryis the issue ID'projects'-- List projects in the connected Sentry org'events'-- Discover-style event table search.queryis a Sentry search expression
Sentry Search Syntax
key:value-- exact match (e.g.level:error,environment:production)AND/OR-- combine clauses (e.g.level:error AND environment:production)!key:value-- negationkey:[a,b]-- value in list>,<,>=,<=-- comparison on numeric/date fields*-- wildcard- Common keys:
level,environment,release,project,is,assigned,bookmarks,has
stats_period
- Format:
Nmminutes,Nhhours,Nddays,Nwweeks (e.g.24h,7d,30m) - Defaults to
24hif omitted
Common Searches
- Unresolved errors:
query_sentry(resource_type='issues', query='is:unresolved level:error', stats_period='24h') - Production fatal errors:
query_sentry(resource_type='issues', query='level:fatal environment:production', stats_period='1h') - Errors in a specific release:
query_sentry(resource_type='issues', query='release:v1.2.3 is:unresolved') - Issue details:
query_sentry(resource_type='issue_detail', query='1234567890') - Full stacktrace for an issue:
query_sentry(resource_type='issue_event', query='1234567890') - All projects:
query_sentry(resource_type='projects') - Events from a user:
query_sentry(resource_type='events', query='user.email:[email protected]', stats_period='6h')
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.
- 5d ago First seen · 93 lines · 28 tokens per session scan A 17189bdd050a
sentry is a skill published in the GitHub repository Arvo-AI/aurora (404 stars, last pushed today), licensed Apache-2.0. It adds 28 tokens to every session and 1,214 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
cloud-iam-deep
GCP/AWS/Azure cloud exploitation -- Cloud Functions, Firestore, Cloud Run, S3, MinIO, Blob Storage, SA keys.
isaac-automator
Deploy and operate a cloud Isaac Workstation with Isaac Automator: provision a GPU VM running Isaac Sim, Isaac Lab, and/or Isaac Lab Arena on AWS, GCP, Azure, or Alibaba Cloud, connect to it, move data in and out, control cost with stop/start, repair, import existing deployments, and destroy. Use when the user wants a…
awesome-kubernetes-ops
This skill documents the local verification, editing, and deployment procedures for the Antigravity AI Agent when pair-programming with the repository maintainer.
Cloud Security & Container Hardening
AWS/Azure/GCP security auditing, container and Kubernetes hardening, Infrastructure as Code scanning, and cloud compliance assessment.
console-audit
Audit the running app via chrome-devtools MCP — console errors/warnings + failed/slow network by default; perf (LCP/CLS) and Lighthouse (a11y/SEO) are opt-in. Token-efficient (compacts findings in-browser via a console/network hook); the report is shown inline in the response — no files to open. Target one tab / an…
create-issue
Create GitHub issues using repo templates (feature, bug, spike).