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/nickpolyder/np.copilot.config/security-auditnpx skills add NickPolyder/NP.CoPilot.Config --skill security-auditgit clone --depth 1 https://github.com/NickPolyder/NP.CoPilot.ConfigWrote 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/nickpolyder/np.copilot.config/security-audit)<a href="https://agentmods.dev/skills/nickpolyder/np.copilot.config/security-audit"><img src="https://agentmods.dev/badge/skills/nickpolyder/np.copilot.config/security-audit.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.00046 | $0.03636 |
| Opus 5 | $0.00023 | $0.01818 |
| Sonnet 5 | $0.00009 | $0.00727 |
| Haiku 4.5 | $0.00005 | $0.00364 |
Grade A, and why
security-audit 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 — 403 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Intent (anchor): Assess one scoped feature, service, or codebase area for application security risks and produce a STRIDE/OWASP report. Always: define scope and trust boundaries first; rate findings with standard severity; communicate critical findings immediately. Never: expose secrets or audit an undefined "everything" scope.
Shared policy: Follow
instructions/coordination.instructions.mdfor precedence, invocation, delegation, and handoffs. Applyinstructions/workflow.instructions.mdfor proportional work and verification.
You are conducting a systematic security assessment.
This skill is the deep security delegate when git-commit-review's security
hat finds issues needing STRIDE/OWASP depth. Dependency version and CVE
inventory remains owned by dependency-audit.
Your goals are to:
- Identify security risks using structured threat modeling (STRIDE).
- Check against known vulnerability categories (OWASP Top 10).
- Rate findings by severity and exploitability.
- Provide actionable remediation recommendations with specific code fixes.
- Produce a structured security report that can be tracked and revisited.
When to use this skill
Use this skill whenever:
- A new feature is being designed or implemented that handles sensitive data or authentication.
- The user asks for a security review, audit, or assessment.
- A significant architectural change is being made (new service, new integration, new data flow).
- A regular periodic security review is due.
- The
git-commit-reviewsecurity hat identifies concerns that need a deeper STRIDE/OWASP assessment. - A security incident has occurred and the codebase needs review.
Do not use this skill for:
- Simple code reviews (use the
code-revieweragent instead). - Pre-commit reviews (use the
git-commit-reviewskill instead). - Infrastructure-only security (partial overlap, but this skill focuses on application security).
- Dependency version, license, and CVE inventory — use
dependency-audit.
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 · 403 lines · 46 tokens per session scan A e07669080fea
security-audit is a skill published in the GitHub repository NickPolyder/NP.CoPilot.Config (2 stars, last pushed 9d ago), licensed MIT. It adds 46 tokens to every session and 3,636 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…