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 addxai/enterprise-harness-engineering --skill sentrygit clone --depth 1 https://github.com/addxai/enterprise-harness-engineeringWrote 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/addxai/enterprise-harness-engineering/sentry)<a href="https://agentmods.dev/skills/addxai/enterprise-harness-engineering/sentry"><img src="https://agentmods.dev/badge/skills/addxai/enterprise-harness-engineering/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.1 | $0.00068 | $0.01126 |
| Opus 5 | $0.00034 | $0.00563 |
| Sonnet 5 | $0.00014 | $0.00225 |
| Haiku 4.5 | $0.00007 | $0.00113 |
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 7d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sentry
Query errors, investigate exceptions, track issues, and monitor release health via the Sentry REST API. API usage is referenced through Context7 MCP; only company-specific rules are documented here.
Description
Applicable scenarios: production error investigation, issue triage, release health checks, crash analysis.
- Internal URL:
https://sentry-us.example.com(self-hosted Sentry, API base path/api/0/) - Organization slug:
sentry
| Variable | Description | Required |
|---|---|---|
SENTRY_AUTH_TOKEN |
Organization Token (Settings -> Organization Tokens -> Create) | Yes |
Authentication: -H "Authorization: Bearer $SENTRY_AUTH_TOKEN"
The current Organization Token only has Release-related permissions by default. To query Issues/Events, create an Internal Integration in Developer Settings and enable
Issue & Event: Read,Project: Read,Organization: Read.
Rules
Project Structure (7 projects)
| Project slug | Product | Platform | Description |
|---|---|---|---|
app-android |
Main App | Android | Primary consumer app (most frequent releases) |
app-ios |
Main App | iOS | Primary consumer app |
backend-service |
Backend | Java | Backend service (shares releases with consumer-service) |
consumer-service |
Backend | Java | Backend consumer service |
app2-android |
Sub-brand App | Android | Sub-brand app |
app2-ios |
Sub-brand App | iOS | Sub-brand app |
app3-ios |
Security App | iOS | Security app |
Release Version Naming Convention
Three formats, distinguished by platform:
| Platform | Format | Example |
|---|---|---|
| Android | {major}.{minor}.{patch}({commit_hash}) |
2.85.0(b4f16c) |
| iOS | {bundle_id}@{version}+{build_number} |
[email protected]+30713 |
| Backend | {YYYYMMDD}@{COMMIT_HASH} |
20260212@3A5AE26 |
iOS Bundle ID Reference:
| Bundle ID | Product |
|---|---|
com.example.app |
Main App |
com.example.guard |
Guard App |
com.example.app2 |
Sub-brand App |
com.example.app3 |
Security App |
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.
- 7d ago First seen · 107 lines · 68 tokens per session scan A ac1a1f7891e0
sentry is a skill published in the GitHub repository addxai/enterprise-harness-engineering (44 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 68 tokens to every session and 1,126 once invoked, about $0.0003 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
bug-diagnosis
Use this skill to systematically diagnose the root cause of a bug before attempting a fix. Activates when a bug is reported, a test is failing, or unexpected behavior is observed. Prevents guess-and-check debugging that introduces additional bugs while chasing symptoms.
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
systematic-debugging
A step-by-step method for finding the underlying cause of technical problems before changing code. It covers reading errors, reproducing failures, checking recent changes, and tracing data across system components.
peon-ping-toggle
Toggle peon-ping sound notifications on/off. Use when user wants to mute, unmute, pause, or resume peon sounds during a Claude Code session. Also handles config changes like volume, pack rotation, categories — any peon-ping setting.
peon-ping-log
Log exercise reps for the Peon Trainer. Use when user says they did pushups, squats, or wants to log reps. Examples - "/peon-ping-log 25 pushups", "/peon-ping-log 30 squats", "log 50 pushups".
diagnose-backend-bug
Diagnose a bounded backend or multi-service failure from GitHub Issues, Jira, Aone, user-provided exports, logs, traces, responses, stack traces, or job records. Use when a service, API, RPC, worker, queue, CLI, or scheduled job bug needs correlation through the project's existing observability route before repair; do…