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/cheezy/stride-security-review/security-review-essentialsnpx skills add cheezy/stride-security-review --skill security-review-essentialsgit clone --depth 1 https://github.com/cheezy/stride-security-reviewWrote 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/cheezy/stride-security-review/security-review-essentials)<a href="https://agentmods.dev/skills/cheezy/stride-security-review/security-review-essentials"><img src="https://agentmods.dev/badge/skills/cheezy/stride-security-review/security-review-essentials.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.00144 | $0.02124 |
| Opus 5 | $0.00072 | $0.01062 |
| Sonnet 5 | $0.00029 | $0.00425 |
| Haiku 4.5 | $0.00014 | $0.00212 |
Grade A, and why
security-review-essentials 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 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.
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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
security-review-essentials
This skill documents how to invoke the AI-powered security review delivered by the security-review plugin. It tells you when to invoke and what the output means. The analysis methodology itself lives in the security-reviewer agent prompt — do not duplicate it here.
When to invoke
The plugin supports two scan modes — pick the one that matches the question you are asking.
Diff mode (default) answers "is this change safe to merge?" Invoke it before any of the following:
- Pushing a PR that touches authentication, authorization, session handling, or password/token handling.
- Pushing a PR that touches cryptography (hashing, signing, encryption, random number generation for security purposes).
- Pushing a PR that touches user input handling, query building, shell-outs, file uploads, redirects, or response rendering.
- Merging code into
mainor any deployment branch when the diff is large enough that a manual security read is impractical. - A human reviewer asks "did you run a security check on this?"
Full mode (--full) answers "what latent issues are in this codebase right now?" Invoke it for:
- Onboarding the plugin onto an existing repo for the first time — establish a baseline before you start gating PRs.
- Periodic posture checks (quarterly, or on a cron) so latent issues outside the recent diff surface get a regular look.
- Vendoring-in / forking an upstream codebase — review the imported code end-to-end before integrating it.
- Investigating a class-wide concern ("audit our use of cryptography across the repo") where the changed code is not the unit of interest.
Diff vs. full scan
| Aspect | Diff mode (default) | Full mode (--full) |
|---|---|---|
| Question answered | Is this change safe to merge? | What latent issues are in this codebase right now? |
| Input | Working-tree diff against HEAD |
Tracked files via git ls-files, filtered by binary heuristic and a 256 KiB size cap |
| Cost | One agent dispatch | One dispatch per batch of ~10 files (batches may run in parallel) |
| Typical cadence | Per PR | Onboarding, quarterly, or on demand |
| Output schema | Identical — same JSON document | Identical — same JSON document |
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 · 125 lines · 144 tokens per session scan A ea45effc32a3
security-review-essentials is a skill published in the GitHub repository cheezy/stride-security-review (5 stars, last pushed 15d ago), licensed MIT. It adds 144 tokens to every session and 2,124 once invoked, about $0.0007 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.
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…
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…