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/scaffoldnpx skills add NickPolyder/NP.CoPilot.Config --skill scaffoldgit 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/scaffold)<a href="https://agentmods.dev/skills/nickpolyder/np.copilot.config/scaffold"><img src="https://agentmods.dev/badge/skills/nickpolyder/np.copilot.config/scaffold.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.00038 | $0.01524 |
| Opus 5 | $0.00019 | $0.00762 |
| Sonnet 5 | $0.00008 | $0.00305 |
| Haiku 4.5 | $0.00004 | $0.00152 |
Grade A, and why
scaffold 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Intent (anchor): Generate new code boilerplate that matches the project's existing architecture, conventions, and layer boundaries. Always: discover conventions first; confirm files before writing; include relevant tests and wiring. Never: overwrite existing files or use scaffolding as a full feature workflow.
Shared policy: Follow
instructions/coordination.instructions.mdfor precedence, invocation, delegation, and handoffs. Applyinstructions/workflow.instructions.mdfor proportional work and verification.
You are scaffolding new application code structures that follow the project's established architecture.
Your goals are to:
- Generate consistent boilerplate that respects existing conventions.
- Enforce layer boundaries — scaffolded code has correct dependencies from the start.
- Reduce manual setup — let the developer focus on business logic, not plumbing.
- Include test infrastructure — every scaffolded component gets a corresponding test file/project.
When to use this skill
Use this skill whenever:
- Creating a new service, aggregate, entity, or feature module from scratch.
- Adding a new project/layer to an existing solution (e.g., new bounded context).
- The user asks to "generate", "scaffold", "create a new [component]", or "set up a [pattern]".
- Bootstrapping a new API endpoint with full vertical slice (controller → handler → domain → tests).
Do not use this skill for:
- Modifying existing code — that's regular implementation or the
refactorskill. - Generating a full feature (design + tasks + implementation) — use
prd-workflow. - One-off code snippets — just write them directly.
- Agent/docs configuration, repository operating manuals, or docs memory
skeletons — use
repo-bootstrapinstead.
How it works
Phase 1: Discover Conventions
Before generating anything, understand what already exists:
- Read project config — check
.github/instructions/project-config.instructions.mdfor tech stack. - Identify patterns — look at existing code for naming, folder structure, namespace conventions.
- Detect architecture style — Clean Architecture layers, vertical slices, or project-specific layout.
- Find templates — check if the project has its own scaffolding templates or item templates.
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 · 167 lines · 38 tokens per session scan A f76f68aef039
scaffold is a skill published in the GitHub repository NickPolyder/NP.CoPilot.Config (2 stars, last pushed 9d ago), licensed MIT. It adds 38 tokens to every session and 1,524 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…