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 repo-bootstrapgit 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/repo-bootstrap)<a href="https://agentmods.dev/skills/nickpolyder/np.copilot.config/repo-bootstrap"><img src="https://agentmods.dev/badge/skills/nickpolyder/np.copilot.config/repo-bootstrap.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.1 | $0.00071 | $0.02456 |
| Opus 5 | $0.00036 | $0.01228 |
| Sonnet 5 | $0.00014 | $0.00491 |
| Haiku 4.5 | $0.00007 | $0.00246 |
Grade A, and why
repo-bootstrap 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 6d 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 — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Intent (anchor): Bootstrap one repository with a tailored Copilot agent contract and durable docs working-memory skeleton. Always: analyze the repo before interviewing; tailor templates with verified commands; get approval before writing or overwriting files. Never: copy raw templates verbatim or commit generated files.
Shared policy: Follow
instructions/coordination.instructions.mdfor precedence, invocation, delegation, and handoffs. Applyinstructions/workflow.instructions.mdfor proportional work and verification.
You are bootstrapping a repository so that any Copilot agent working in it has a clear contract and a durable, file-based working memory — the same structure that makes agent-driven repos effective:
- A tight
.github/copilot-instructions.mdcontract: repository mission, agent role, hard rules, verified commands, delivery capabilities, and handover conventions. - A
docs/memory tree the agent reads before working and updates as it goes:PLAN.md(canonical design),TASKS.md(phased execution), plusdecisions/,features/,handoffs/,reviews/,retrospectives/.
This is bootstrap only: it seeds the agent/docs configuration baseline. It does not maintain docs, write detailed ADR/feature/retrospective content, or implement application code.
Your goals:
- Tailor, don't dump. Interview the user and analyze the repo, then generate content specific to this repo — never copy raw templates verbatim.
- Extend, don't contradict. The repo-level config layers on top of the
global
~/.copilot/config. Reference global conventions; don't restate them. - Be safe and idempotent. Never overwrite existing files without explicit approval. Augment a partial structure instead of clobbering it.
When to use this skill
Use this skill whenever:
- A repo has no
.github/copilot-instructions.mdand/or nodocs/working structure, and the user wants agents to work in it effectively. - The user asks to "bootstrap", "onboard this repo for Copilot", "set up the agent operating manual", or "give this repo the AgentMemory structure".
- An existing repo's instructions/docs are ad-hoc and need a consistent baseline.
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.
- 6d ago First seen · 236 lines · 71 tokens per session scan A d1342fc142f9
repo-bootstrap is a skill published in the GitHub repository NickPolyder/NP.CoPilot.Config (2 stars, last pushed 12d ago), licensed MIT. It adds 71 tokens to every session and 2,456 once invoked, about $0.0004 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.