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/foru17/neko-master/copilot-instructionsgit clone --depth 1 https://github.com/foru17/neko-masterWrote 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/foru17/neko-master/copilot-instructions)<a href="https://agentmods.dev/instructions/foru17/neko-master/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/foru17/neko-master/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.00118 | $0.00118 |
| Opus 5 | $0.00059 | $0.00059 |
| Sonnet 5 | $0.00024 | $0.00024 |
| Haiku 4.5 | $0.00012 | $0.00012 |
Grade A, and why
neko-master 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 Instructions
All repo guidance lives in AGENTS.md — commands, code conventions, key contracts, and the project map. Follow it.
Task-specific workflow guides (plain Markdown, tool-agnostic) are in .claude/skills/: verify-changes, add-stats-dimension, release, ui-conventions, db-conventions, agent-probe-dev. Consult the matching guide before changes to stats/schema, UI, releases, or the Go agent.
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 · 6 lines · 118 tokens per session scan A bd4f891dd2d1
neko-master copilot-instructions.md is an instructions file published in the GitHub repository foru17/neko-master (3,861 stars, last pushed 1mo ago), licensed MIT. It adds 118 tokens to every session, about $0.0006 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
yaml-proxy-editor AGENTS.md
AGENTS.md instructions for NextWeb4/yaml-proxy-editor, covering agents.md, 1. project structure, 2. run commands, 3. test commands and 4. build commands.
Vibe-Research AGENTS.md
AGENTS.md instructions for simonlin1212/Vibe-Research, covering vibe-research-agent 金融研究宪法, 0. 三条不可越线, 1. 数据纪律(五问 gate:给出任何数字或结论前逐条自问), 2. 研究哲学(评估框架,不是预测工具) and 3. 估值口径(你只选输入、解释输出;计算交给 calc/).
pygwalker CLAUDE.md
Instructions for Kanaries/pygwalker, covering claude.md and tl;dr for a coding agent.
worldmonitor AGENTS.md
AGENTS.md instructions for koala73/worldmonitor, covering agents.md, task mode and authority, start here, surface routing and architecture invariants.
vizro copilot-instructions.md
Copilot instructions for mckinsey/vizro, covering github copilot instructions for vizro, pull requests from bots and automated tooling and everything else.
TreeMap-Disk-Visualizer AGENTS.md
Instructions for Prithvi-Web/TreeMap-Disk-Visualizer, covering treemap for agents, two ways in, the core workflow: scan → inspect → dry-run → act, the safety model (enforced server-side, not advisory) and mcp specifics.