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/pilotspace/pilot-space/scan-securitynpx skills add pilotspace/pilot-space --skill scan-securitygit clone --depth 1 https://github.com/pilotspace/pilot-spaceWrote 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/pilotspace/pilot-space/scan-security)<a href="https://agentmods.dev/skills/pilotspace/pilot-space/scan-security"><img src="https://agentmods.dev/badge/skills/pilotspace/pilot-space/scan-security.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.00030 | $0.01316 |
| Opus 5 | $0.00015 | $0.00658 |
| Sonnet 5 | $0.00006 | $0.00263 |
| Haiku 4.5 | $0.00003 | $0.00132 |
Grade A, and why
scan-security 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 3d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scan Security Skill
Perform automated security scanning on code blocks in the current note. Checks for OWASP Top 10 vulnerabilities, authentication/authorization gaps, SQL injection, XSS, insecure deserialization, and project-specific security patterns (RLS enforcement, API key exposure).
Quick Start
Use this skill when:
- User requests a security scan (
/scan-security) - Agent detects code handling user input, database queries, or authentication
- User asks "is this secure?" or "check for vulnerabilities"
Example:
User: "Scan this authentication endpoint for security issues"
AI scans:
- A01: Broken Access Control — missing workspace_id filter?
- A02: Cryptographic Failures — plain-text tokens, weak hashing?
- A03: SQL Injection — raw string interpolation in queries?
- A07: Authentication Failures — JWT validation gaps?
- Project-specific: RLS context set? API keys from Vault?
Workflow
-
Collect Code for Scanning
- Read all code blocks from the current note
- Use
search_note_contentto find related auth/validation code in note - Identify the code category: API endpoint, service, repository, frontend component
-
Run OWASP Top 10 Checks
- A01 Broken Access Control: Missing
workspace_idfilter, role checks, RLS enforcement - A02 Cryptographic Failures: Plain-text secrets, weak hash algorithms (MD5/SHA1), HTTP vs HTTPS
- A03 Injection: SQL string interpolation, template injection, command injection, path traversal
- A05 Security Misconfiguration: Debug mode in prod, exposed stack traces, CORS wildcard
- A07 Authentication Failures: Token validation gaps, missing expiry checks, JWT
nonealg - A08 Software Integrity Failures: Untrusted deserialization, unsafe
pickle, eval usage
- A01 Broken Access Control: Missing
-
Run Project-Specific Checks
- RLS: Is
get_workspace_context()called before every DB query? - API Keys: Are secrets fetched from
SecureKeyStorage(Vault), not env vars directly in prod code? - Input Validation: Is all user input validated through Pydantic v2 schemas?
- SSE Endpoints: Are workspace membership checks done before streaming?
- RLS: Is
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.
- 3d ago First seen · 140 lines · 30 tokens per session scan A a726f83b22f2
scan-security is a skill published in the GitHub repository pilotspace/pilot-space (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 1,316 once invoked, about $0.0002 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…