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/ai-ready/copilot-instructionsgit clone --depth 1 https://github.com/johnpapa/ai-readyWrote 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/ai-ready/copilot-instructions)<a href="https://agentmods.dev/instructions/johnpapa/ai-ready/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/johnpapa/ai-ready/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 | $0.00516 | $0.00516 |
| Opus 5 | $0.00258 | $0.00258 |
| Sonnet 5 | $0.00103 | $0.00103 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
ai-ready 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 4d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions — ai-ready
Project Type
This is a Copilot CLI skill containing only markdown, YAML, and JSON files. There is no source code, no build system, no test framework, and no runtime dependencies.
Do not generate or suggest build commands, test commands, package installs, or runtime setup for this repo.
Writing Conventions
Markdown
- Use ATX-style headings (
#,##,###) - Use fenced code blocks with language identifiers (
yaml,bash, ```json) - Use tables for structured data — always include a header row
- Keep lines under 120 characters where practical
- Use
**bold**for emphasis,_italic_for terms,`backticks`for file paths and commands
YAML (skill frontmatter, workflows, issue templates)
- Use 2-space indentation
- Quote strings that contain special YAML characters
- Always include
nameanddescriptionin skill frontmatter
JSON
- Use 2-space indentation
Skill Writing Conventions
- Each step should be independently actionable — the AI should be able to execute it without context from other steps
- Include explicit "check if exists" guards before creating files
- Use real file paths and real commands, not placeholders
- Prefer structured output (tables) over prose for analysis results
- Always end with a summary step listing what was created, skipped, and what to do next
Maintenance Matrix
| When this changes... | Also update... |
|---|---|
skills/ai-ready/SKILL.md |
README.md (if skill behavior changed), docs/how-it-works.md, AGENTS.md, CHANGELOG.md |
skills/ai-ready/references/* |
Verify consistency with SKILL.md steps that reference them |
New skill added to skills/ |
README.md, AGENTS.md (structure section), CHANGELOG.md |
docs/how-it-works.md |
Verify consistency with SKILL.md steps and README.md |
README.md problem statement or architecture |
Verify consistency with docs/how-it-works.md |
| Repo structure changes (new dirs, moved files) | AGENTS.md (structure section), CHANGELOG.md |
Version bump (SKILL.md metadata, plugin.json) |
CHANGELOG.md, GitHub Release |
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.
- 4d ago First seen · 48 lines · 516 tokens per session scan A 6adf4bdb2f3a
ai-ready copilot-instructions.md is an instructions file published in the GitHub repository johnpapa/ai-ready (123 stars, last pushed 1mo ago), licensed MIT. It adds 516 tokens to every session, about $0.0026 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
skill-recorder copilot-instructions.md
Instructions for microsoft/skill-recorder, covering repository instructions for coding agents and pull requests target the active release branch, not main.
copilotd copilot-instructions.md
Instructions for DamianEdwards/copilotd, covering copilot instructions for copilotd, build & run, build, run from source (auto-builds and passes all args through) and architecture.
DPlex copilot-instructions.md
Copilot instructions for Ron537/DPlex, covering dplex — copilot instructions, build & run, architecture, process boundaries and provider system (ai tool abstraction).
spec-kit-copilot AGENTS.md
Instructions for github/spec-kit-copilot, covering what this repository is, core skills plugin, core decisions (do not silently undo) and when revving the core skills plugin.
claude-plugins CLAUDE.md
Instructions for peterblazejewicz/claude-plugins, covering claude.md, repository overview, plugin architecture, command files and plugin: avalonia-dev.
oh-my-copilot AGENTS.md
AGENTS.md instructions for RobinNorberg/oh-my-copilot, covering oh-my-copilot - intelligent multi-agent orchestration, working agreements, setup and review guidelines.