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/adithyan-ak/agenthound/copilot-instructionsgit clone --depth 1 https://github.com/adithyan-ak/AgentHoundWrote 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/adithyan-ak/agenthound/copilot-instructions)<a href="https://agentmods.dev/instructions/adithyan-ak/agenthound/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/adithyan-ak/agenthound/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.00015 | $0.00015 |
| Opus 5 | $0.00008 | $0.00008 |
| Sonnet 5 | $0.00003 | $0.00003 |
| Haiku 4.5 | $0.00002 | $0.00002 |
Grade A, and why
AgentHound 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.
What it actually says
Copilot Fixture Instructions
Keep generated examples local to the fixture project.
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 · 4 lines · 15 tokens per session scan A 185ca7a4523c
AgentHound copilot-instructions.md is an instructions file published in the GitHub repository adithyan-ak/AgentHound (344 stars, last pushed today), licensed Apache-2.0. It adds 15 tokens to every session, about $0.0001 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
a2a-demos copilot-instructions.md
Instructions for capiscio/a2a-demos, covering a2a-demos - github copilot instructions, ⛔ absolute rules - no exceptions, 1. all work via pull requests, 2. no watch/blocking commands and 🚨 critical: read first.
mcpkernel copilot-instructions.md
Copilot instructions for piyushptiwari1/mcpkernel, covering mcpkernel — project context for all agents, project overview, architecture, code standards and build & test.
mcpkernel testing-guidelines.instructions.md
Use when writing or modifying tests for MCPKernel. Covers pytest patterns, async testing, fixtures, and test structure.
mcpkernel policy-writing.instructions.md
Use when working with MCPKernel YAML policy files. Covers policy syntax, rule structure, OWASP ASI mappings, and best practices for writing security policies.
mcpkernel python-conventions.instructions.md
Use when writing or modifying Python code in MCPKernel. Covers async patterns, type hints, structlog logging, error handling, and module conventions.
RedTeam-Agent copilot-instructions.md
Copilot instructions for ktol1/RedTeam-Agent, covering repository instructions, preferred execution model, terminal execution contract, tool location and output discipline.