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 getsentry/dotagents --skill dotagents-qagit clone --depth 1 https://github.com/getsentry/dotagentsWrote 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/getsentry/dotagents/dotagents-qa)<a href="https://agentmods.dev/skills/getsentry/dotagents/dotagents-qa"><img src="https://agentmods.dev/badge/skills/getsentry/dotagents/dotagents-qa/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/getsentry/dotagents/dotagents-qa"><img src="https://agentmods.dev/badge/skills/getsentry/dotagents/dotagents-qa.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.00059 | $0.01648 |
| Opus 5.5 | $0.00024 | $0.00659 |
| Sonnet 5.5 | $0.00012 | $0.00330 |
| Haiku 4.5 | $0.00006 | $0.00165 |
Grade A, and why
dotagents-qa 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.
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dotagents QA
Prove the requested behavior in Docker without touching host agent homes, caches, plugin registries, or credentials. Treat Docker as the safety boundary and the changed or released behavior as the test plan.
1. Define the contract
Before commands, state:
- the exact subject: local checkout, packed local build, or published version;
- the commands and semantics at risk;
- default-global scope, explicit-project scope, or both;
- the harnesses involved;
- the fixture and evidence that constitute a pass.
For a published release, verify its registry metadata and install that exact version. Never silently test the local checkout instead. If you fix a discovered defect, report the release failure and packed-local-build pass separately.
Read the relevant references before acting:
- Docker, non-root setup, exact release installation, and baseline commands: references/docker-sandbox.md
- Ordinary install/sync behavior: references/core-agentic-qa.md
- Real plugins, full lifecycle, native clients, and user/global scope: references/release-plugin-matrix.md
- Plugin adapters and automated proof: references/plugin-runtime.md
- Harness details: Claude, Copilot, Codex, OpenCode, Pi, Cursor, Grok
Planning is part of acting: read the relevant references before proposing a command sequence, not only before executing it.
2. Establish isolation
Use the repo QA image. Rebuild it when the Dockerfile, pnpm version, or required current harness versions changed.
Run package and runtime work as a non-root user. Keep these inside Docker or disposable directories:
export HOME=/sandbox/home
export DOTAGENTS_STATE_DIR=/sandbox/state
export DOTAGENTS_HOME=/sandbox/user-agents
export COPILOT_HOME=/sandbox/copilot-home
export CODEX_HOME=/sandbox/codex-home
export CLAUDE_CONFIG_DIR=/sandbox/claude-home
What ships with it
25 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- Dockerfile 764 B
- evals/cases/define-the-qa-contract.yaml 602 B
- evals/cases/enforce-docker-isolation.yaml 533 B
- evals/cases/exercise-complete-cli-lifecycles.yaml 567 B
- evals/cases/prove-each-harness-independently.yaml 640 B
- evals/cases/report-evidence-and-limits.yaml 1.5 KB
- evals/cases/run-proportionate-baseline-validation.yaml 532 B
- evals/cases/test-representative-real-plugins.yaml 566 B
- evals/cases/verify-project-scope-migration-edges.yaml 594 B
- evals/cases/verify-scope-flag-compatibility.yaml 512 B
- evals/cases/verify-scope-reversal-release.yaml 560 B
- references/claude.md 2.6 KB
- references/codex.md 2.5 KB
- references/copilot.md 2.8 KB
- references/core-agentic-qa.md 1.4 KB
- references/cursor.md 1.7 KB
- references/docker-sandbox.md 2.5 KB
- references/grok.md 1.6 KB
- references/opencode.md 4.8 KB
- references/pi.md 1.1 KB
- references/plugin-runtime.md 3.6 KB
- references/release-plugin-matrix.md 6.5 KB
- scripts/qa-example.mjs 30 KB runs code
- SOURCES.md 3.3 KB
- spec.md 5.6 KB
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 Changed · +2 lines · +3 tokens per session 7642ee40a85f
- 1mo ago First seen · 128 lines · 56 tokens per session scan A 7775fd90d9d1
dotagents-qa is a skill published in the GitHub repository getsentry/dotagents (253 stars, last pushed yesterday), licensed MIT. It adds 59 tokens to every session and 1,648 once invoked, about $0.0002 per session on Opus 5.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
sentry-snapshots-cocoa
Full Sentry Snapshots setup for Apple/Cocoa projects. Use when asked to "setup SnapshotPreviews", "setup Apple snapshot testing", "upload Apple snapshots to Sentry", "setup Apple snapshot GitHub Actions", or "setup Apple selective snapshot testing".
sentry-snapshots-cocoa
Full Sentry Snapshots setup for Apple/Cocoa projects. Use when asked to "setup SnapshotPreviews", "setup Apple snapshot testing", "upload Apple snapshots to Sentry", "setup Apple snapshot GitHub Actions", or "setup Apple selective snapshot testing".
sentry-snapshots-cocoa
Full Sentry Snapshots setup for Apple/Cocoa projects. Use when asked to "setup SnapshotPreviews", "setup Apple snapshot testing", "upload Apple snapshots to Sentry", "setup Apple snapshot GitHub Actions", or "setup Apple selective snapshot testing".
sentry-debug-issue
Debug and fix a Sentry issue — find it (by link, ID, or search), pull full context (stack trace, breadcrumbs, trace, logs), optionally run Seer root-cause / autofix, apply the code fix, and resolve it via a Fixes PROJECT-NAME-12A commit/PR. Use when working a known error or hunting one down to fix.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.