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.
Borrowing it
Nothing to install: this file belongs to johnpapa/vscode-peacock. 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/johnpapa/vscode-peacock/main/.claude/skills/ai-ready/SKILL.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/skills/johnpapa/vscode-peacock/ai-ready)<a href="https://agentmods.dev/skills/johnpapa/vscode-peacock/ai-ready"><img src="https://agentmods.dev/badge/skills/johnpapa/vscode-peacock/ai-ready/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/johnpapa/vscode-peacock/ai-ready"><img src="https://agentmods.dev/badge/skills/johnpapa/vscode-peacock/ai-ready.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Agent Snooping · line 165 Skill accesses MCP server configuration files (mcp.json). MCP configs contain server URLs, authentication tokens, and tool definitions — reading them allows the skill to discover and potentially abuse other tool integrations.Fix: Remove all code or instructions that read MCP configuration files (mcp.json). MCP server details should be managed by the agent runtime, not read by individual skills.
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.00107 | $0.03440 |
| Opus 5 | $0.00053 | $0.01720 |
| Sonnet 5 | $0.00021 | $0.00688 |
| Haiku 4.5 | $0.00011 | $0.00344 |
Grade B, and why
ai-ready scanned grade B 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 3d 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.
Reads MCP configurationmediumAgent snooping
mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.
If missing, generate `.mcp.json` at the repo root based on detected dependencies (databases, APIs, cloud platforms, browser automation, DevOps tools). Use `${VAR}` for secrets. Only include servers the project actually n Copies of this mod
1 near-identical copy found in the catalogue:
- ai-ready — 97% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI-Ready Repo Skill
Persona
Adopt the perspective of an experienced repo maintainer who has managed high-traffic repos and reviewed thousands of PRs. Prioritize what reduces review burden and contributor friction. Every file you generate should earn its place — generic boilerplate creates noise.
Follow these steps in order to analyze the current repository and generate all missing AI-ready configuration assets.
First run vs. re-run: On the first run, most assets will be missing — the skill creates them. On re-runs, it audits existing assets against the current codebase, checking for drift, stale content, and new conventions from recent PR reviews. The skill never overwrites existing files without user approval.
Skipping assets: If the user's prompt mentions skipping specific assets (e.g., "skip CI and issue templates"), respect those exclusions. Still run the full analysis, but skip generation for the excluded assets.
Report-only mode: If the user asks for a report without generating files (e.g., "how ai-ready is this repo?", "score this repo"), run the full analysis (Steps 0–1) and display the report (Step 11) — but skip all generation steps (Steps 2–10).
The 12 tracked assets
Assets are grouped into three categories. Count assets with Nailed It status for the score.
🤖 AI Context — what AI agents read to understand your repo
| # | Asset | Generated in |
|---|---|---|
| 1 | AGENTS.md |
Step 2 |
| 2 | .github/copilot-instructions.md |
Step 3 |
| 3 | Maintenance matrix (in copilot-instructions.md) |
Step 8 |
| 4 | .mcp.json |
Step 4b |
| 5 | .github/workflows/copilot-setup-steps.yml |
Step 4 |
🔧 Dev Workflow — what keeps PRs clean and contributors on track
| # | Asset | Generated in |
|---|---|---|
| 6 | CI workflow (.github/workflows/ci.yml) |
Step 5 |
| 7 | Issue templates (.github/ISSUE_TEMPLATE/) |
Step 6 |
| 8 | PR template (.github/PULL_REQUEST_TEMPLATE.md) |
Step 6 |
| 9 | .github/dependabot.yml |
(checked, not generated) |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 249 lines · 107 tokens per session scan B 2f686f46584f
ai-ready is a skill published in the GitHub repository johnpapa/vscode-peacock (1,177 stars, last pushed yesterday), licensed MIT. It adds 107 tokens to every session and 3,440 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 1 finding (reads mcp configuration). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-06.
Other skills, from other repositories
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
project-setup-info-local
Comprehensive setup steps to help the user create complete project structures in a VS Code workspace; this tool is designed for full project initialization and scaffolding, not for creating individual files. When to use this tool: user wants to create a new complete project from scratch; setting up entire project…
update-skills
Create or update repository skills and instructions when major learnings are discovered during a session. Use when the user says "learn!", when a significant pattern or pitfall is identified, or when reusable domain knowledge should be captured for future sessions.
github-copilot-upgrader
Use this to update the Github Copilot CLI/SDK.
commit
Commit staged or unstaged changes with an AI-generated commit message that matches the repository's existing commit style. Use when the user asks to 'commit', 'commit changes', 'create a commit', 'save my work', or 'check in code'.
sync
Sync the current session branch with its upstream branch, or publish the current session branch to a remote. Use when the user asks to sync a branch, pull latest changes, rebase onto upstream, push current branch, publish branch, or set upstream.