Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/NickPolyder/NP.CoPilot.Confignpx agentmods add skills/nickpolyder/np.copilot.config/repo-bootstrapWrote 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/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/repo-bootstrap"><img src="https://agentmods.dev/badge/skills/nickpolyder/np.copilot.config/repo-bootstrap.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.00071 | $0.03572 |
| Opus 5.5 | $0.00028 | $0.01429 |
| Sonnet 5.5 | $0.00014 | $0.00714 |
| Haiku 4.5 | $0.00007 | $0.00357 |
Grade C, and why
repo-bootstrap scanned grade C with 1 finding 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- np-copilot-capabilities-owner: .github/instructions/project-config.instructions.md --> How it starts
The opening of the file, as written. The whole thing — 328 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 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.
- Preserve continuity ownership. Existing project/cross-agent records and a configured session-memory provider coexist; a docs skeleton is not permission to generate duplicate per-session handover exports.
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.
- 1mo ago Changed · +92 lines scan A → C a6351ece8451
- 1mo 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 1mo ago), licensed MIT. It adds 71 tokens to every session and 3,572 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…