Borrowing it
Nothing to install: this file belongs to drujensen/aiagent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/drujensen/aiagent/main/.claude/skills/security-review/SKILL.mdgit clone --depth 1 https://github.com/drujensen/aiagentWrote 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/drujensen/aiagent/security-review)<a href="https://agentmods.dev/skills/drujensen/aiagent/security-review"><img src="https://agentmods.dev/badge/skills/drujensen/aiagent/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/drujensen/aiagent/security-review"><img src="https://agentmods.dev/badge/skills/drujensen/aiagent/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.00063 | $0.00471 |
| Opus 5.5 | $0.00025 | $0.00188 |
| Sonnet 5.5 | $0.00013 | $0.00094 |
| Haiku 4.5 | $0.00006 | $0.00047 |
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 4d 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
Security review for:
Instructions
You are orchestrating a Security Review cycle for the aiagent project.
Phase 1: Security Analysis
- Use the Agent tool with
subagent_type: "security"to analyze the code - Pass it the feature description and list of changed files (if known)
- The security agent will:
- Run grep-based scans for command injection, path traversal, API key leakage, MongoDB injection patterns
- Review each changed file against the project's threat model
- Propose specific remediations for any issues found
Phase 2: Review
4. Use the Agent tool with subagent_type: "security-reviewer" to review the security analysis
5. Pass the security agent's full output to the reviewer
6. The reviewer will independently run the automated security scans and score against the 6 pillars
Phase 3: Iterate 7. If overall score >= 8/10 (APPROVED): Report the security posture and scores 8. If overall score < 8/10 (REVISE):
- Extract Critical Issues from the reviewer
- Send issues back to the security agent for remediation proposals
- Re-review with the security-reviewer
- Repeat until APPROVED or 3 iterations maximum
Phase 4: Report 9. Present:
- Security findings summary
- Remediations applied or recommended
- Final pillar scores table
- Any remaining warnings
Important
- Maximum 3 review iterations
- The security agent PROPOSES FIXES; the reviewer only READS and SCORES
- Critical issues (injection vulnerabilities, key leakage) block shipping
- Warnings are non-blocking but should be tracked
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.
- 4d ago First seen · 50 lines · 63 tokens per session scan A 03ba1516f9bc
security-review is a skill published in the GitHub repository drujensen/aiagent (5 stars, last pushed 2mo ago), licensed MIT. It adds 63 tokens to every session and 471 once invoked, about $0.0003 per session on Opus 5.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-10-03.
Other skills, from other repositories
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…