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/documentationnpx skills add NickPolyder/NP.CoPilot.Config --skill documentationgit clone --depth 1 https://github.com/NickPolyder/NP.CoPilot.ConfigWhat 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.00042 | $0.03046 |
| Opus 5 | $0.00021 | $0.01523 |
| Sonnet 5 | $0.00008 | $0.00609 |
| Haiku 4.5 | $0.00004 | $0.00305 |
Grade A, and why
documentation 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 — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Intent (anchor): Create or update project documentation in
docs/so it stays synchronized with code, decisions, APIs, and user-visible behavior. Always: follow the existing docs structure; update indexes when adding documents; consult the relevant specialist for domain accuracy. Never: duplicate specialist workflows or override markdown-style instructions.
Shared policy: Follow
instructions/coordination.instructions.mdfor precedence, invocation, delegation, and handoffs. Applyinstructions/workflow.instructions.mdfor proportional work and verification.
You are helping maintain project documentation in the docs/ folder.
Your goals are to:
- Keep documentation in sync with code changes — every feature addition, modification, or removal should be reflected in docs.
- Own docs placement, index maintenance, cross-references, and synchronization with code/user-visible behavior.
- Follow the established docs structure and the applicable markdown-style instruction instead of redefining style here.
- Ensure documentation is comprehensive and actionable.
- Consult specialist agents for domain-specific accuracy and recommend specialist skills for deep ADR, test, or security work (see Agent Consultation below).
When to use this skill
Use this skill whenever:
- You add, change, or remove functionality in the codebase.
- The user asks to document something.
- You create a new feature, endpoint, page, or entity.
- Infrastructure or deployment changes are made.
- An architecture decision is recorded; recommend
architecture-decision-recordfor ADR content and use this skill for placement, index, and sync. - A feature plan is finalized (coordinate with the
feature-planningskill). - UX specifications or wireframes need to be documented.
Rule: Always update docs/ when adding, changing, or removing functionality.
Agent consultation
Different documentation types benefit from specialist agent input. Consult the appropriate agent to ensure accuracy and completeness.
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 · 348 lines · 42 tokens per session scan A d5d35c514415
documentation is a skill published in the GitHub repository NickPolyder/NP.CoPilot.Config (2 stars, last pushed 7d ago), licensed MIT. It adds 42 tokens to every session and 3,046 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…