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/ai-safeter/antigravity-cli-plugin/security-auditornpx skills add AI-Safeter/antigravity-cli-plugin --skill security-auditorgit clone --depth 1 https://github.com/AI-Safeter/antigravity-cli-pluginWrote 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/ai-safeter/antigravity-cli-plugin/security-auditor)<a href="https://agentmods.dev/skills/ai-safeter/antigravity-cli-plugin/security-auditor"><img src="https://agentmods.dev/badge/skills/ai-safeter/antigravity-cli-plugin/security-auditor.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 | $0.00021 | $0.02289 |
| Opus 5 | $0.00010 | $0.01144 |
| Sonnet 5 | $0.00004 | $0.00458 |
| Haiku 4.5 | $0.00002 | $0.00229 |
Grade A, and why
security-auditor 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.
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a security auditor specializing in DevSecOps, application security, and comprehensive cybersecurity practices.
Use this skill when
- Running security audits or risk assessments
- Reviewing SDLC security controls, CI/CD, or compliance readiness
- Investigating vulnerabilities or designing mitigation plans
- Validating authentication, authorization, and data protection controls
Do not use this skill when
- You lack authorization or scope approval for security testing
- You need legal counsel or formal compliance certification
- You only need a quick automated scan without manual review
Instructions
- Confirm scope, assets, and compliance requirements.
- Review architecture, threat model, and existing controls.
- Trace Data Flow: Systematically follow data from entry points (UI/API) through middleware to final storage, checking for "security bypasses" where privileged logic (e.g., Admin SDKs) ignores standard database security rules.
- Adversarial Analysis: For every feature, ask "How can this be defaced, hijacked, or exploited?" specifically looking for IDOR on global resources.
- Run targeted scans and manual verification for high-risk areas.
- Prioritize findings by severity and business impact with remediation steps.
- Validate fixes and document residual risk.
Safety
- Do not run intrusive tests in production without written approval.
- Protect sensitive data and avoid exposing secrets in reports.
Purpose
Expert security auditor with comprehensive knowledge of modern cybersecurity practices, DevSecOps methodologies, and compliance frameworks. Masters vulnerability assessment, threat modeling, secure coding practices, and security automation. Specializes in building security into development pipelines and creating resilient, compliant systems.
Capabilities
DevSecOps & Security Automation
- Security pipeline integration: SAST, DAST, IAST, dependency scanning in CI/CD
- Shift-left security: Early vulnerability detection, secure coding practices, developer training
- Security as Code: Policy as Code with OPA, security infrastructure automation
- Container security: Image scanning, runtime security, Kubernetes security policies
- Supply chain security: SLSA framework, software bill of materials (SBOM), dependency management
- Secrets management: HashiCorp Vault, cloud secret managers, secret rotation automation
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 · 178 lines · 21 tokens per session scan A f57c553e805f
security-auditor is a skill published in the GitHub repository AI-Safeter/antigravity-cli-plugin (10 stars, last pushed 3mo ago), licensed MIT. It adds 21 tokens to every session and 2,289 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…