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/benrben/mpga/securenpx skills add benrben/MPGA --skill securegit clone --depth 1 https://github.com/benrben/MPGAWhat 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.00024 | $0.01449 |
| Opus 5 | $0.00012 | $0.00724 |
| Sonnet 5 | $0.00005 | $0.00290 |
| Haiku 4.5 | $0.00002 | $0.00145 |
Grade A, and why
mpga-secure 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 2d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
secure
Security audit time. We're going to expose every hole, every weakness, every DISASTER hiding in this codebase. Security is NON-NEGOTIABLE. Complete and total shutdown of untested code until every vulnerability is patched.
Trigger: User wants a security audit, vulnerability check, or security review. Also triggered by: "security audit", "check for vulnerabilities", "find secrets", "is this secure", "security scan".
Delegation
This skill orchestrates a security-auditor agent — the toughest, most thorough auditor you've ever seen — with three parallel scan lanes. We hit them from EVERY angle, believe me:
- Dependency vulnerability audit — we check EVERY package, no exceptions
- Secrets scanning — we find EVERYTHING. Nobody hides secrets from us.
- OWASP Top 10 pattern analysis — the TEN COMMANDMENTS of security. You break them, we find you.
Protocol
-
Spawn security-auditor agent to coordinate the full security audit. This agent is a WINNER. It does not miss things.
-
Dependency audit — if
requirements.txtorpyproject.tomlexists:pip audit 2>/dev/nullParse the JSON output to extract:
- Vulnerability count by severity (critical, high, moderate, low)
- Affected packages and versions
- Available fix versions
- CVE references where available
If no
requirements.txtorpyproject.toml, skip this step and note it in the report. We don't waste time on things that aren't there. We're SMART. -
Secrets scan — search the codebase for leaked credentials. This is HUGE. Leaked secrets are a TOTAL DISASTER and we will find every single one:
- API keys (patterns:
AKIA,sk-,pk_live_,ghp_,xoxb-) - Hardcoded passwords (patterns:
password\s*=\s*["'],secret\s*=\s*["']) - Private keys (
-----BEGIN.*PRIVATE KEY-----) - Connection strings with embedded credentials
.envfiles committed to git (checkgit ls-filesfor.env*)- JWT tokens and bearer tokens in source
- Check
.gitignorefor proper exclusion of sensitive files
- API keys (patterns:
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.
- 2d ago First seen · 108 lines · 24 tokens per session scan A 2b01611b3942
mpga-secure is a skill published in the GitHub repository benrben/MPGA (5 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 1,449 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…