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/nirecom/agents/review-plan-securitynpx skills add nirecom/agents --skill review-plan-securitygit clone --depth 1 https://github.com/nirecom/agentsWrote 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/nirecom/agents/review-plan-security)<a href="https://agentmods.dev/skills/nirecom/agents/review-plan-security"><img src="https://agentmods.dev/badge/skills/nirecom/agents/review-plan-security.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.00021 | $0.00700 |
| Opus 5 | $0.00010 | $0.00350 |
| Sonnet 5 | $0.00004 | $0.00140 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
review-plan-security 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 today.
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 — 29 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review security implications of the implementation plan via Codex (single round, no re-loop).
Procedure
RPS-1. Resolve <PLANS_DIR> via skills/_shared/resolve-plans-dir.md. Identify <PLANS_DIR>/<session-id>-detail.md. Initialize EXTENSIONS_USED=0.
RPS-2. Invoke "$AGENTS_CONFIG_DIR/skills/review-plan-security/scripts/run-codex-review-loop.sh" (Bash), exporting AGENTS_CONFIG_DIR, SESSION_ID, PLANS_DIR, EXTENSIONS_USED. Pass CTX_SURVEY_CODE, CTX_SURVEY_HISTORY, CTX_CONCERNS_LOG as env vars when available. Exit-code handling (SSOT: skills/_shared/codex-review-loop.md; single-round — no re-loop):
- exit 0 APPROVED → RPS-4 (no RISK items).
- exit 1 NEEDS_REVISION → terminal; save stdout to
<PLANS_DIR>/<session-id>-security-plan-codex-round-<N>-raw.md(<N>from<PLANS_DIR>/<session-id>-security-plan-last-round.txt); present concerns with per-axis severity; propose mitigations; stop (no re-loop) → RPS-3. - exit 2 ESCALATE → run
review-loop-summarize-concerns --budget-remaining 0; present summary; stop → RPS-3. - exit 6 HIGH_UNRESOLVED → save stdout to
<PLANS_DIR>/<session-id>-security-plan-codex-round-<N>-raw.md(<N>from<PLANS_DIR>/<session-id>-security-plan-last-round.txt); runreview-loop-summarize-concerns --budget-remaining 0; present unresolved HIGH concerns; stop → RPS-3. - exit 3 → silently launch
plan-security-reviewersubagent; use its verdict for RPS-4. - exit 4 → HALT with blocking error; surface wrapper stderr; do NOT launch fallback agent.
- exit 5 → does not occur (MAX_EXTENSIONS=0); treat as exit 4 HALT if received.
- exit 7 FINALIZE_FAILED →
<PLANS_DIR>/<session-id>-security-plan-unresolved-concerns.jsoncould not be written; HALT, surface the## Concern Ledger: FINALIZE-FAILEDline, launch no fallback, emit no sentinel. After an ESCALATE, confirm the artifact with"$AGENTS_CONFIG_DIR/bin/concern-ledger" check-finalized --plans-dir <PLANS_DIR> --session-id <session-id> --format security-planfirst. RPS-3. Present concerns with per-axis severity and proposed mitigations before implementation proceeds. RPS-4. Summary — APPROVED: report no RISK items; NEEDS_REVISION: summarize mitigations.
What ships with it
1 file 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.
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.
- today Changed · -1 lines 2a34476192ba
- 3d ago First seen · 30 lines · 21 tokens per session scan A 6045c20b529b
review-plan-security is a skill published in the GitHub repository nirecom/agents (3 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 700 once invoked, about $0.0001 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…