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.
git clone --depth 1 https://github.com/vb-nattamai/agent-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/vb-nattamai/agent-ready/copilot-instructions)<a href="https://agentmods.dev/instructions/vb-nattamai/agent-ready/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/vb-nattamai/agent-ready/copilot-instructions/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/instructions/vb-nattamai/agent-ready/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/vb-nattamai/agent-ready/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00578 | $0.00578 |
| Opus 5.5 | $0.00231 | $0.00231 |
| Sonnet 5.5 | $0.00116 | $0.00116 |
| Haiku 4.5 | $0.00058 | $0.00058 |
Grade A, and why
agent-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 1mo 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions — hello_world
Project Summary
A minimal Flask REST API (Python ≥ 3.11) that serves personalised greetings, records them in an in-memory list, and exposes health-check and listing endpoints. All logic lives in a single module (app.py). No database or external services are involved.
Commands
| Action | Command |
|---|---|
| Install | pip install -r requirements.txt |
| Install (editable/dev) | detected as likely: pip install -e . — verify before use |
| Run | python app.py |
| Test | pytest |
Module Layout
app.py — Flask app object, all four REST endpoints, in-memory greetings list
tests/
test_app.py — pytest tests for all API endpoints via Flask test client
Restricted Paths
Restricted write paths: Not determinable from source — fill in agent-context.json static.restricted_write_paths after reviewing your repo.
Never do without updating tests:
- Rename or remove any public endpoint:
/,/health,/greet/<name>,/greetings - Rename the Flask variable
appinapp.py— tests import it directly - Introduce a database dependency without migration/setup instructions
Key Domain Concepts
| Term | Definition |
|---|---|
| Greeting | A recorded personalised message containing a user's name and a hello message, stored in the in-memory list. |
| Health Check | A lightweight endpoint (/health) that returns an ok status to confirm the service is running. |
| Service Root | The index endpoint (/) that returns the service name and version metadata. |
Top 3 Pitfalls
- Stale in-memory state in tests —
_greetingsis a module-level list that persists across requests within a process. Tests that do not reset the list between runs will see data from previous tests, causing false failures or false passes.
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.
- 1mo ago First seen · 58 lines · 578 tokens per session scan A 3d19d89813c1
agent-ready copilot-instructions.md is an instructions file published in the GitHub repository vb-nattamai/agent-ready (6 stars, last pushed 2mo ago), licensed MIT. It adds 578 tokens to every session, about $0.0023 per session on Opus 5.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-31.
Other instructions, from other repositories
graftcode graftcode-python.instructions.md
Instructions for grft-dev/graftcode, covering graftcode — python backend services, when this applies (always), authoritative docs (source of truth), golden rules and service = plain python module (no web framework).
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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).