Borrowing it
Nothing to install: this file belongs to VersoXBT/claude-initial-setup. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/VersoXBT/claude-initial-setup/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/VersoXBT/claude-initial-setupWrote 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/instructions/versoxbt/claude-initial-setup/copilot-instructions)<a href="https://agentmods.dev/instructions/versoxbt/claude-initial-setup/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/versoxbt/claude-initial-setup/copilot-instructions/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/instructions/versoxbt/claude-initial-setup/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/versoxbt/claude-initial-setup/copilot-instructions.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.01474 | $0.01474 |
| Opus 5.5 | $0.00590 | $0.00590 |
| Sonnet 5.5 | $0.00295 | $0.00295 |
| Haiku 4.5 | $0.00147 | $0.00147 |
Grade A, and why
claude-initial-setup copilot-instructions.md 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions
Code Style
Always create new objects instead of mutating existing ones. Use spread operators, structuredClone, or immutable patterns like @dataclass(frozen=True) in Python and value receivers in Go.
Never use .push(), .pop(), .splice(), .sort(), or .reverse() on shared arrays. Use [...arr, item], .filter(), .map(), .toSorted(), and .toReversed() instead.
Keep files between 200-400 lines. Extract separate modules when files grow beyond 800 lines. Organize files by feature or domain, not by type.
Keep functions under 50 lines. If longer, extract helper functions with descriptive names.
Avoid nesting deeper than 4 levels. Use early returns, guard clauses, or extracted functions to flatten logic.
Name variables to describe WHAT they contain, not HOW they were computed. Use activeUsers instead of data or result.
Prefix boolean variables with is, has, can, should, was, or will: isActive, hasPermission, canEdit.
Name functions with a verb describing what they do: getUserById, formatDate, validateEmail, createOrder.
Use plural nouns for collections: users, orderItems. Use singular for individual items in iteration.
Use SCREAMING_SNAKE_CASE for true constants: MAX_RETRIES, API_BASE_URL.
Follow language-specific casing: camelCase for JS/TS variables, PascalCase for classes/types, snake_case for Python, PascalCase for exported Go identifiers.
Git Workflow
Use conventional commits: <type>(<scope>): <description>. Types: feat, fix, refactor, docs, test, chore, perf, ci.
Write commit messages in imperative mood ("add feature" not "added feature"), lowercase after type, under 72 characters, no trailing period.
Name branches as feature/, fix/, hotfix/, release/ followed by ticket ID and kebab-case description: feature/AUTH-123-add-sso-login.
Keep pull requests under 400 lines. Include a summary, list of changes, and test plan in every PR description.
Never rebase commits that have been pushed to a shared branch. Never force-push to main or develop.
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 First seen · 158 lines · 1,474 tokens per session scan A 3d77f8ca4b62
claude-initial-setup copilot-instructions.md is an instructions file published in the GitHub repository VersoXBT/claude-initial-setup (4 stars, last pushed 5mo ago), licensed MIT. It adds 1,474 tokens to every session, about $0.0059 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.