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 skills add jy315189/everything-cursor --skill security-reviewgit clone --depth 1 https://github.com/jy315189/everything-cursorWrote 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/jy315189/everything-cursor/security-review)<a href="https://agentmods.dev/skills/jy315189/everything-cursor/security-review"><img src="https://agentmods.dev/badge/skills/jy315189/everything-cursor/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/jy315189/everything-cursor/security-review"><img src="https://agentmods.dev/badge/skills/jy315189/everything-cursor/security-review.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.02498 |
| Opus 5.5 | $0.00000 | $0.00999 |
| Sonnet 5.5 | $0.00000 | $0.00500 |
| Haiku 4.5 | $0.00000 | $0.00250 |
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 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.
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 — 328 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Review Skill
Comprehensive security audit methodology for web applications.
When to Use
Activate this skill when:
- Reviewing code for security vulnerabilities
- Implementing authentication or authorization
- Handling user input or file uploads
- Working with sensitive data (PII, credentials, tokens)
- Preparing for a security audit or penetration test
1. OWASP Top 10 Quick Reference
A01: Broken Access Control
→ Check: Every endpoint validates permissions. No IDOR.
→ Test: Can user A access user B's data by changing the ID?
A02: Cryptographic Failures
→ Check: Passwords hashed with bcrypt/argon2. TLS everywhere.
→ Test: Are secrets in env vars? Is sensitive data encrypted at rest?
A03: Injection
→ Check: Parameterized queries. No string concatenation in SQL.
→ Test: Does ' OR 1=1-- in an input cause unexpected behavior?
A04: Insecure Design
→ Check: Rate limiting on auth endpoints. Account lockout.
→ Test: Can brute-force succeed? Is there business logic abuse?
A05: Security Misconfiguration
→ Check: No debug mode in production. Secure headers set.
→ Test: Are stack traces exposed? Default credentials removed?
A06: Vulnerable Components
→ Check: Dependencies up to date. No known CVEs.
→ Test: Run `npm audit`. Check Snyk/Dependabot alerts.
A07: Authentication Failures
→ Check: Strong password policy. MFA available. Session timeout.
→ Test: Can sessions be hijacked? Are tokens properly invalidated?
A08: Software/Data Integrity
→ Check: Signed packages. Integrity checks on CI/CD.
→ Test: Can deployment pipeline be tampered with?
A09: Logging & Monitoring Failures
→ Check: Auth events logged. Anomaly detection in place.
→ Test: Are failed login attempts logged? Alerts configured?
A10: SSRF
→ Check: Validate/whitelist URLs for server-side requests.
→ Test: Can internal endpoints be accessed via user-supplied URLs?
2. Input Validation Patterns
Defense in Depth: Validate at Every Layer
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 · 328 lines · 0 tokens per session scan A 96b06f3d7932
security-review is a skill published in the GitHub repository jy315189/everything-cursor (2 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,498 tokens. 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
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…