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 instructions/johnpapa/vscode-winteriscoming/copilot-instructionsgit clone --depth 1 https://github.com/johnpapa/vscode-winteriscomingWrote 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/johnpapa/vscode-winteriscoming/copilot-instructions)<a href="https://agentmods.dev/instructions/johnpapa/vscode-winteriscoming/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/johnpapa/vscode-winteriscoming/copilot-instructions.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.00641 | $0.00641 |
| Opus 5 | $0.00320 | $0.00320 |
| Sonnet 5 | $0.00128 | $0.00128 |
| Haiku 4.5 | $0.00064 | $0.00064 |
Grade A, and why
vscode-winteriscoming 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 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions — Winter is Coming Theme
Project Type
This is a VS Code color theme extension. There is no runtime code, no build step, and no test framework. The deliverables are JSON theme files and the package.json manifest.
Theme Editing Conventions
Color Values
- Use hex color codes in lowercase:
#219fd5, not#219FD5 - Include alpha channel only when transparency is intentional:
#219fd544 - Keep accent colors consistent across dark variants (
#219fd5blue,#C792EApurple,#f7ecb5yellow)
Token Colors
- Use VS Code's
tokenColorsarray withscope(string or array) andsettings(foreground,fontStyle) - Use TextMate scope names — reference the VS Code syntax highlighting guide
- When adding a new token rule, add it to all 6 theme files (or at minimum to both the italics and no-italics variants of the affected base theme)
Workbench Colors
- Use the VS Code theme color reference for valid property names
- Test contrast for accessibility — ensure text is readable against backgrounds
Italics vs No-Italics
- The "No Italics" variants must have zero
"fontStyle": "italic"entries - When modifying a token in a base theme, apply the same color change to the no-italics variant but do not add
"fontStyle": "italic"
File Conventions
JSON
- Use 2-space indentation (consistent with VS Code defaults)
- Theme files do not have a JSON schema reference — they follow the VS Code color theme format implicitly
package.json
contributes.themesmust list every theme file with correctlabel,uiTheme, andpath- Bump
versionon every release - Do not add runtime dependencies — this extension has none
Images
- Screenshots go in
images/as PNG files - Use descriptive names:
dark-blue-ts.png,light-js.png - Keep image dimensions consistent for README display
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 · 60 lines · 641 tokens per session scan A c0fa0242f9f8
vscode-winteriscoming copilot-instructions.md is an instructions file published in the GitHub repository johnpapa/vscode-winteriscoming (182 stars, last pushed 1mo ago), licensed MIT. It adds 641 tokens to every session, about $0.0032 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-30.
Other instructions, from other repositories
awesome-vscode CLAUDE.md
Instructions for viatsko/awesome-vscode, covering claude.md, what this repo is, adding an entry, themes and linting / ci.
kilocode AGENTS.md
AGENTS.md instructions for Kilo-Org/kilocode, covering agents.md, build and dev, quality checks, products and package instructions.
vscode-peacock AGENTS.md
AGENTS.md instructions for johnpapa/vscode-peacock, covering peacock — agent guide, project overview, repository structure, tech stack and build & run.
language-tools AGENTS.md
AGENTS.md instructions for prisma/language-tools, covering agent guide for prisma language tools, project overview, packages, documentation and quick start.
getspecstory copilot-instructions.md
Copilot instructions for specstoryai/getspecstory: Examine the file changes for the pull request.
vscode-peacock copilot-instructions.md
Copilot instructions for johnpapa/vscode-peacock, covering copilot instructions — peacock, project type, typescript conventions, vs code extension patterns and color handling.