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/usefulsoftwareco/executor/warden-security-reviewnpx skills add UsefulSoftwareCo/executor --skill warden-security-reviewgit clone --depth 1 https://github.com/UsefulSoftwareCo/executorWhat 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.00055 | $0.01327 |
| Opus 5 | $0.00028 | $0.00664 |
| Sonnet 5 | $0.00011 | $0.00265 |
| Haiku 4.5 | $0.00006 | $0.00133 |
Grade A, and why
warden-security-review scanned grade A with 1 finding 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
rg -l "\b(exec|spawn|execFile|fork|subprocess|Deno\.Command|new Function|eval\(|vm\.|QuickJS|quickjs|Worker\(|import\(|compile|instantiate|runIn|shell|command|child_process)\b" \ Copies of this mod
1 near-identical copy found in the catalogue:
- warden-security-review — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Warden security review runbook
Use Warden as a first-pass scanner, then manually verify every finding against the code. A clean Warden run means "no findings from that skill/pass", not "the codebase is secure."
Setup
Warden uses Claude Code auth locally. For Claude Max usage:
claude login
Run Warden through npm so the package version does not need to be committed:
npm exec --yes --package=@sentry/warden -- warden --help
The repo has a warden.toml that uses remote skills from getsentry/warden-skills.
Reference skills are mirrored under .reference/warden-skills when needed. .reference/ is gitignored.
Local Outputs
Write run artifacts under .warden-runs/. Do not commit .warden/ or .warden-runs/.
Use JSONL output for later triage:
mkdir -p .warden-runs
npm exec --yes --package=@sentry/warden -- \
warden <targets...> --skill <skill> --fail-on off --report-on low --min-confidence low \
--parallel 2 --log -o .warden-runs/<name>.jsonl
Warden may not treat bare directories as recursive targets. Prefer explicit quoted globs or a target file list.
Recommended Scans
Authz on cloud/API surfaces:
npm exec --yes --package=@sentry/warden -- \
warden "apps/cloud/src/auth/**/*.ts" "apps/cloud/src/api/**/*.ts" \
"apps/cloud/src/routes/**/*.tsx" "packages/core/api/src/**/*.ts" \
--skill wrdn-authz --fail-on off --report-on low --min-confidence low \
--parallel 2 --log -o .warden-runs/authz.jsonl
Code execution on sink-bearing runtime/plugin files:
rg -l "\b(exec|spawn|execFile|fork|subprocess|Deno\.Command|new Function|eval\(|vm\.|QuickJS|quickjs|Worker\(|import\(|compile|instantiate|runIn|shell|command|child_process)\b" \
apps/local/src/server apps/cli/src packages/core/execution/src packages/core/sdk/src packages/kernel packages/plugins \
-g "*.ts" -g "*.tsx" -g "!*.test.ts" -g "!*.spec.ts" -g "!*.e2e.ts" -g "!**/dist/**" -g "!**/node_modules/**" \
> .warden-runs/code-execution-targets.txt
npm exec --yes --package=@sentry/warden -- \
warden $(tr '\n' ' ' < .warden-runs/code-execution-targets.txt) \
--skill wrdn-code-execution --fail-on off --report-on low --min-confidence low \
--parallel 2 --log -o .warden-runs/code-execution.jsonl
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 · 121 lines · 55 tokens per session scan A 046e7c90e2d6
warden-security-review is a skill published in the GitHub repository UsefulSoftwareCo/executor (3,494 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 1,327 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.