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/warpdotdev/oz-for-oss/security-review-prnpx skills add warpdotdev/oz-for-oss --skill security-review-prgit clone --depth 1 https://github.com/warpdotdev/oz-for-ossWrote 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/warpdotdev/oz-for-oss/security-review-pr)<a href="https://agentmods.dev/skills/warpdotdev/oz-for-oss/security-review-pr"><img src="https://agentmods.dev/badge/skills/warpdotdev/oz-for-oss/security-review-pr.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.1 | $0.00066 | $0.01650 |
| Opus 5 | $0.00033 | $0.00825 |
| Sonnet 5 | $0.00013 | $0.00330 |
| Haiku 4.5 | $0.00007 | $0.00165 |
Grade A, and why
security-review-pr 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Fetching scripts over HTTP or piping curl to a shell inside build or CI steps. How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Review PR Skill
Audit the current pull request for security concerns and fold any findings into the same review.json produced by the base review-pr skill.
Goal
Provide a focused security pass on top of the general PR review. This is a supplement to review-pr, not a separate output. Findings must be merged into the single combined review.json so reviewers receive one cohesive review.
Inputs
- The working directory is the PR branch checkout.
- The workflow usually provides an annotated diff in
pr_diff.txt. - The workflow usually provides the PR description in
pr_description.md. - Focus on the files and lines changed by this PR.
- Default behavior: do not post comments or reviews to GitHub directly.
When to apply this skill
- Apply on code PRs whenever
review-pris applied. - Do not apply on spec-only PRs handled by
review-spec. - Skip the skill entirely when no changed file introduces code or configuration that touches the concerns below; it is better to stay silent than to manufacture findings.
- Do not duplicate findings the base
review-prpass will already raise. If the base review would naturally catch an issue, leave it there rather than re-reporting it from the security pass.
Security concerns to audit
Evaluate each changed hunk against the following concerns. Treat the list as a checklist, not a ceiling — flag other clearly security-relevant issues when they appear.
Input validation and untrusted data
- User-supplied or network-supplied input used without validation, length limits, or type checks.
- Deserialization of untrusted data (e.g.
pickle,yaml.load,eval,Function,JSON.parsefeeding into a command). - Path traversal risk: user input concatenated into filesystem paths without normalization or an allowlist.
- SSRF risk: user-controlled URLs passed to outbound HTTP clients without scheme or host restrictions.
- Unbounded resource use driven by untrusted input (memory, loops, regex with catastrophic backtracking).
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.
- 6d ago First seen · 117 lines · 66 tokens per session scan A 34d11ddacfdf
security-review-pr is a skill published in the GitHub repository warpdotdev/oz-for-oss (307 stars, last pushed 4d ago), licensed MIT. It adds 66 tokens to every session and 1,650 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…