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 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/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<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="Reviewed on agentmods" width="80" 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.1 | $0.00038 | $0.01766 |
| Opus 5.5 | $0.00015 | $0.00706 |
| Sonnet 5.5 | $0.00008 | $0.00353 |
| Haiku 4.5 | $0.00004 | $0.00177 |
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 1mo 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
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 applicable tests — cover scaffolded behavior with the existing runner; do not create a test project merely for boilerplate with no behavior.
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 contracts — check
.github/instructions/project-config.instructions.md,.github/copilot-instructions.md, and relevant existingAGENTS.md,CLAUDE.md, orGEMINI.mdfor the target's stack and commands. - 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.
- Select target verification — resolve the component/workspace being changed, its command entry points, and working directories from project contracts, manifests, and existing CI/scripts. Record the exact command, cwd, and coverage before generation. In a mixed repo, choose the changed component, not an unrelated root project just because its toolchain is available.
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.
- 1mo ago Changed · +16 lines d0b6a0bbdc17
- 1mo 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 1mo ago), licensed MIT. It adds 38 tokens to every session and 1,766 once invoked, about $0.0002 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…