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/rjmurillo/ai-agents/copilot-instructionsgit clone --depth 1 https://github.com/rjmurillo/ai-agentsWrote 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/rjmurillo/ai-agents/copilot-instructions)<a href="https://agentmods.dev/instructions/rjmurillo/ai-agents/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/rjmurillo/ai-agents/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.01113 | $0.01113 |
| Opus 5 | $0.00557 | $0.00557 |
| Sonnet 5 | $0.00223 | $0.00223 |
| Haiku 4.5 | $0.00111 | $0.00111 |
Grade A, and why
ai-agents 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 yesterday.
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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot Instructions
IMPORTANT: File minimal. Cut context bloat. Detail in AGENTS.md.
Global Behavioral Steering
For cross-harness behavior rules, local Copilot sessions can also read
~/.copilot/copilot-instructions.md. AGENTS.md remains this repository's
primary reference for ai-agents-specific rules.
Copilot Cloud cannot read local dotfiles. If you have access to Richard's dotfiles repo, use the branch-agnostic fallback link in Key Documents.
Agent Delegation for Complex Tasks
Multi-step tasks, specialized expertise, big context → prefer delegation via #runSubagent rather than inline handling.
| When to Delegate | Agent | Example Prompt |
|---|---|---|
| Multi-step coordination | orchestrator |
"Implement OAuth 2.0 with tests and docs" |
| Codebase exploration | analyst |
"Investigate why cache invalidation fails" |
| Architecture decisions | architect |
"Design the event sourcing pattern for orders" |
| Implementation work | implementer |
"Implement the UserService per approved plan" |
| Plan validation | critic |
"Review the migration plan for gaps" |
| Security review | security |
"Assess auth flow for vulnerabilities" |
Why delegate:
- Context window efficient (agent start fresh)
- Specialized prompts + constraints
- Focused results to synthesize
Delegation pattern:
#runSubagent orchestrator "Help me implement feature X end-to-end"
Keep inline: Simple single-file edits, quick lookups. No specialized reasoning needed.
Primary Reference
Read AGENTS.md FIRST for full instructions:
- Session protocol (blocking gates)
- Agent catalog + workflows
- Directory structure
- GitHub workflow requirements
- Skill system
- Memory management
- Quality gates
Path: ../AGENTS.md (repo root)
Before changing hooks, hook generators, agents, skills, instructions, rules, or
runtime scripts shared by Claude Code and Copilot CLI, load
agent-harness-reference. Execute contract changes through
ai-agents-portability-campaign. Do not infer one harness from another.
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.
- yesterday First seen · 125 lines · 1,113 tokens per session scan A f0e44ddeda20
ai-agents copilot-instructions.md is an instructions file published in the GitHub repository rjmurillo/ai-agents (45 stars, last pushed today), licensed MIT. It adds 1,113 tokens to every session, about $0.0056 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-09-03.
Other instructions, from other repositories
abtars AGENTS.md
AGENTS.md instructions for aksika/abtars, covering agents.md, quick commands, architecture, model-call chokepoint: spin(spec) (#1271) and external dependency: abmind.
Alex_Skill_Mall mall-maintenance-rules.instructions.md
Always-on routing for Mall maintenance work — fires the right Mall skill at the right moment. Distinguishes Mall-owned automation from out-of-scope editorial work.
gameforge AGENTS.md
Instructions for robcost/gameforge, covering general guidelines for working with nx, scaffolding & generators and when to use nxdocs.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.