Executor is a shared integration layer that lets AI agents use tools from MCP servers, OpenAPI specifications, GraphQL APIs, and custom JavaScript functions through one catalog. It centralizes credentials and per-tool access policies so MCP-compatible agents can reuse the same integrations.
Borrowing it
Nothing to install: this file belongs to UsefulSoftwareCo/executor. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/UsefulSoftwareCo/executor/main/.skills/warden-security-review/SKILL.mdgit clone --depth 1 https://github.com/UsefulSoftwareCo/executorWrote 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/usefulsoftwareco/executor/warden-security-review)<a href="https://agentmods.dev/skills/usefulsoftwareco/executor/warden-security-review"><img src="https://agentmods.dev/badge/skills/usefulsoftwareco/executor/warden-security-review/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/usefulsoftwareco/executor/warden-security-review"><img src="https://agentmods.dev/badge/skills/usefulsoftwareco/executor/warden-security-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 78 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00055 | $0.01327 |
| Opus 5.5 | $0.00022 | $0.00531 |
| Sonnet 5.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 2mo 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.
- 2mo 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 (4,297 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 1,327 once invoked, about $0.0002 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…