Peacock is a Visual Studio Code extension that changes a workspace’s color so users can distinguish between multiple editor windows or shared and remote sessions. It is for developers who need a quick visual way to identify their VS Code workspaces. Its catalogue entries provide instructions and an MCP integration related to the extension.
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-peacock/agents-mdgit clone --depth 1 https://github.com/johnpapa/vscode-peacockWrote 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-peacock/agents-md)<a href="https://agentmods.dev/instructions/johnpapa/vscode-peacock/agents-md"><img src="https://agentmods.dev/badge/instructions/johnpapa/vscode-peacock/agents-md.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 | $0.01938 | $0.01938 |
| Opus 5 | $0.00969 | $0.00969 |
| Sonnet 5 | $0.00388 | $0.00388 |
| Haiku 4.5 | $0.00194 | $0.00194 |
Grade A, and why
vscode-peacock AGENTS.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 5d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Peacock — Agent Guide
Project Overview
Peacock is a Visual Studio Code extension that subtly changes the color of your workspace. It's ideal when you have multiple VS Code instances, use VS Live Share, or use VS Code's Remote features and want to quickly identify which editor is which.
- Publisher: johnpapa
- VS Code Marketplace: Peacock
- Version: See
package.jsonfor the current version
Repository Structure
vscode-peacock/
├── src/ — Extension source code (TypeScript)
│ ├── extension.ts — Extension entry point (activation, command registration)
│ ├── commands.ts — Command implementations (enter color, random, favorites, etc.)
│ ├── apply-color.ts — Core color application logic
│ ├── color-library.ts — Color manipulation utilities (uses tinycolor2)
│ ├── configuration/ — VS Code configuration read/write helpers
│ ├── models/ — TypeScript interfaces, enums, constants, state
│ ├── inputs.ts — User input prompts (color picker, quick pick)
│ ├── statusbar.ts — Status bar color display
│ ├── live-share/ — VS Live Share integration
│ ├── remote/ — Remote development integration
│ ├── test/ — Mocha unit tests
│ ├── logging.ts — Output channel logging
│ ├── mementos.ts — Global state persistence
│ ├── notification.ts — User notifications
│ └── object-library.ts — Object/element management
├── e2e/ — Playwright end-to-end tests (docs screenshots)
├── docs/ — Docsify documentation site
│ ├── guide/ — User guide pages
│ ├── about/ — About pages
│ ├── changelog/ — Changelog page
│ ├── _sidebar.md — Navigation sidebar
│ └── index.html — Docsify entry point
├── resources/ — Extension icons and assets
├── testworkspace/ — Test workspace used by Mocha tests
├── .github/
│ ├── workflows/docs.yml — Docs deploy + Playwright e2e tests
│ ├── ISSUE_TEMPLATE/ — Bug report and feature request templates
│ └── PULL_REQUEST_TEMPLATE/ — PR template
├── webpack.config.js — Webpack bundler config (Node + Web targets)
├── tsconfig.json — TypeScript configuration
├── playwright.config.ts — Playwright e2e test config
└── package.json — Extension manifest, commands, settings, scripts
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.
- 5d ago First seen · 147 lines · 1,938 tokens per session scan A 64b709fdf27a
vscode-peacock AGENTS.md is an instructions file published in the GitHub repository johnpapa/vscode-peacock (1,176 stars, last pushed yesterday), licensed MIT. It adds 1,938 tokens to every session, about $0.0097 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
kilocode AGENTS.md
AGENTS.md instructions for Kilo-Org/kilocode, covering agents.md, build and dev, quality checks, products and package instructions.
awesome-vscode CLAUDE.md
Instructions for viatsko/awesome-vscode, covering claude.md, what this repo is, adding an entry, themes and linting / ci.
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-gitlens AGENTS.md
AGENTS.md instructions for gitkraken/vscode-gitlens, covering gitlens development guide, working style expectations, development environment, development commands and git & repository guidelines.
calva-backseat-driver AGENTS.md
Instructions for BetterThanTomorrow/calva-backseat-driver, covering calva backseat driver - ai agent guide, essential architecture, action/effect system ("ex"), runtime state structure and datascript connections.