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/arroyo-gonzalo/codex-devkit/security-reviewnpx skills add Arroyo-Gonzalo/codex-devkit --skill security-reviewgit clone --depth 1 https://github.com/Arroyo-Gonzalo/codex-devkitWrote 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/arroyo-gonzalo/codex-devkit/security-review)<a href="https://agentmods.dev/skills/arroyo-gonzalo/codex-devkit/security-review"><img src="https://agentmods.dev/badge/skills/arroyo-gonzalo/codex-devkit/security-review.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.00041 | $0.00760 |
| Opus 5 | $0.00020 | $0.00380 |
| Sonnet 5 | $0.00008 | $0.00152 |
| Haiku 4.5 | $0.00004 | $0.00076 |
Grade A, and why
security-review 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 4d 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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Review
Purpose
Identify security risks before they reach production.
Protect confidentiality, integrity, availability, and tenant isolation while preserving repository conventions.
Do not modify code unless explicitly requested.
Workflow
1. Understand the security context
Identify:
- protected assets;
- user roles;
- trust boundaries;
- entry points;
- sensitive operations;
- exposed endpoints;
- integrations;
- authentication model.
Understand who can access what before reviewing implementation.
2. Inspect authentication
Verify:
- authentication mechanism;
- token validation;
- session handling;
- expiration;
- refresh flow;
- logout behavior;
- password handling;
- credential storage.
Do not assume authentication automatically implies authorization.
3. Inspect authorization
Verify:
- permissions;
- ownership;
- role validation;
- tenant isolation;
- resource access;
- administrative operations;
- server-side enforcement.
Never rely only on frontend authorization.
4. Inspect input validation
Review:
- request validation;
- query parameters;
- route parameters;
- uploaded files;
- JSON payloads;
- serialization;
- deserialization;
- type conversion.
Reject invalid input as early as possible.
5. Inspect sensitive data
Review:
- secrets;
- tokens;
- passwords;
- API keys;
- personally identifiable information;
- financial data;
- internal identifiers;
- logs.
Sensitive information should never be unnecessarily exposed.
6. Inspect common vulnerabilities
Review for:
- SQL Injection;
- NoSQL Injection;
- Command Injection;
- XSS;
- CSRF;
- SSRF;
- Path Traversal;
- Open Redirects;
- Insecure File Upload;
- Insecure Deserialization;
- Information Disclosure.
Confirm vulnerabilities before reporting them.
7. Inspect persistence
Verify:
- tenant isolation;
- ownership filters;
- authorization in queries;
- transactions;
- destructive operations;
- soft deletes;
- audit requirements.
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.
- 4d ago First seen · 224 lines · 41 tokens per session scan A b901d2b15887
security-review is a skill published in the GitHub repository Arroyo-Gonzalo/codex-devkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 760 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…