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 airvalona/antigravity-like-claude-code --skill security-reviewgit clone --depth 1 https://github.com/airvalona/antigravity-like-claude-codeWrote 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/airvalona/antigravity-like-claude-code/security-review)<a href="https://agentmods.dev/skills/airvalona/antigravity-like-claude-code/security-review"><img src="https://agentmods.dev/badge/skills/airvalona/antigravity-like-claude-code/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/airvalona/antigravity-like-claude-code/security-review"><img src="https://agentmods.dev/badge/skills/airvalona/antigravity-like-claude-code/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.00054 | $0.00409 |
| Opus 5 | $0.00027 | $0.00204 |
| Sonnet 5 | $0.00011 | $0.00082 |
| Haiku 4.5 | $0.00005 | $0.00041 |
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 — Vulnerability Scan
Port of Claude Code's /security-review. Security-only, unlike code-review
which is general-purpose.
Arguments
/security-review— scan the current uncommitted diff./security-review <target>— scan a specific file, folder, or the whole repo.
Checklist
- Injection: SQL injection, command injection, path traversal, template
injection, unsafe
eval/exec - Secrets: hardcoded API keys, tokens, passwords, credentials committed to the diff or already present in tracked files
- Auth & access control: missing auth checks on new endpoints/handlers, broken object-level authorization, privilege escalation paths
- Input handling: unvalidated/unsanitized user input reaching sensitive sinks (file system, network, shell, DB)
- Dependencies: newly added packages with known CVEs or from untrusted sources (flag for the user to verify — don't fabricate CVE numbers)
- Config: overly permissive CORS, disabled TLS verification, debug mode left on, insecure default credentials
Reporting
For each finding: severity (Critical / High / Medium / Low), file:line, the specific risk, and a concrete fix — not just "sanitize this input" but the actual sanitization approach for that language/framework.
Do not attempt to actually exploit anything found — report only. Do not write or suggest working exploit code, even for demonstration purposes.
Notes
If nothing significant is found, say so plainly rather than manufacturing low-value nits to seem thorough.
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 · 41 lines · 54 tokens per session scan A 7664e1419b98
security-review is a skill published in the GitHub repository airvalona/antigravity-like-claude-code (2 stars, last pushed 2mo ago), licensed MIT. It adds 54 tokens to every session and 409 once invoked, about $0.0003 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…
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
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…