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 Jkudjo/oh-my-cursor --skill security-reviewgit clone --depth 1 https://github.com/Jkudjo/oh-my-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/jkudjo/oh-my-cursor/security-review)<a href="https://agentmods.dev/skills/jkudjo/oh-my-cursor/security-review"><img src="https://agentmods.dev/badge/skills/jkudjo/oh-my-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/jkudjo/oh-my-cursor/security-review"><img src="https://agentmods.dev/badge/skills/jkudjo/oh-my-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.00021 | $0.00288 |
| Opus 5 | $0.00010 | $0.00144 |
| Sonnet 5 | $0.00004 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
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 9d 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.
What it actually says
security-review
Dedicated security audit. More thorough than @review's security section.
When to use
- Before shipping anything that handles auth, user data, or external input
- When adding new API endpoints or third-party integrations
- Periodic security audits of sensitive subsystems
What it covers
- Injection — SQL, command, HTML, template injection
- Auth — broken authentication, missing authorization, JWT issues
- Secrets — hardcoded credentials, tokens, keys in code or git history
- Input validation — unvalidated input reaching dangerous operations
- Dependencies — known CVEs in package.json / requirements
- IDOR — direct object references without ownership checks
- CSRF/XSS — missing protections in web-facing code
- Data exposure — sensitive fields in logs, API responses, or error messages
- Supply chain — suspicious packages, loose version pins
Output
Report with findings:
- Severity: CRITICAL / HIGH / MEDIUM / LOW
- File:line reference
- Attack vector description
- Recommended fix
Verdict: SECURE | ISSUES FOUND (N critical, N high)
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.
- 9d ago First seen · 38 lines · 21 tokens per session scan A edf6ef61ec1e
security-review is a skill published in the GitHub repository Jkudjo/oh-my-cursor (1 stars, last pushed 5mo ago), licensed MIT. It adds 21 tokens to every session and 288 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
architecture
Architecture Design Command 🏗️.
testing-pyramid
Test Distribution Analysis Command 🧪.
dev-workflow
This rule defines the workflow for AI agents to follow when implementing features from user stories, focusing on lean development principles and agile methodologies.
biome
Biome JavaScript/TypeScript linter and formatter.
typescript-standards
TypeScript best practices and coding standards.
git-commit-push
Enforces Git commit standards and conventions when committing and pushing code in Agent Mode. This rule is crucial for keeping track of changes made by agents, and should run whenever the user expresses they want to commit or push code changes made by the agent. This rule should be followed when: 1. the user wants to…