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/zexion7873/copilot-setting/copilot-instructionsgit clone --depth 1 https://github.com/zexion7873/copilot-settingWrote 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/zexion7873/copilot-setting/copilot-instructions)<a href="https://agentmods.dev/instructions/zexion7873/copilot-setting/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/zexion7873/copilot-setting/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.00524 | $0.00524 |
| Opus 5 | $0.00262 | $0.00262 |
| Sonnet 5 | $0.00105 | $0.00105 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
copilot-setting 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 3d 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Global Copilot Instructions
Language & Communication
- Always respond in Traditional Chinese (繁體中文).
- Code, variable names, comments, and commit messages must be in English.
- Keep responses concise and direct.
Tech Stack
- Java 8 — WAR packaging, deployed to servlet container (not embedded server)
- Maven
- Spring Framework 3.2 — not 4.x/5.x. No
@RestController, no@Conditional. XML config +<tx:advice>for transactions - Spring Security 3.2 — XML namespace config
- Hibernate 4.2 — native Session API (not JPA),
hbm.xmlmappings (not annotations),getCurrentSession() - MySQL 8.0 — InnoDB, utf8mb4
- SLF4J 1.7 + Logback
- JSP + JSTL 1.2 — view layer
Hard boundary — not a style preference. Do NOT use APIs, annotations, or patterns from newer versions of these frameworks. The pull toward modern idioms is a bias to resist, not a hint to follow — and the build won't catch it: many such symbols compile clean and fail only at review or runtime. If unsure whether something exists in these versions, read the matching instructions/ file before writing code; never guess.
Coding Philosophy
- State assumptions explicitly. If uncertain, ask — don't guess.
- If multiple interpretations exist, present them. Don't pick silently.
- Prefer what already exists — a codebase pattern, the stdlib, an already-installed dependency — before writing new code.
- Minimum code that solves the problem — no speculative abstractions, no features beyond what was asked.
- Touch only what the task requires; match existing style, even if you'd do it differently.
- Clean up orphans YOUR changes created. Don't remove pre-existing dead code — mention it, don't delete it.
File Operations
- Never use
cat/echo/printf/teewith>/>>/<< EOFto write file content — VS Code terminal integration corrupts these (tab completion, escaping, exit 130). - Create / modify files with the file editing tools (Write / Edit).
- Terminal remains fine for package management, builds, tests, git,
ls/mkdir/rm, and downloads that don't pipe into files.
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.
- 3d ago First seen · 36 lines · 524 tokens per session scan A d36e007a4293
copilot-setting copilot-instructions.md is an instructions file published in the GitHub repository zexion7873/copilot-setting (1 stars, last pushed 1mo ago), licensed MIT. It adds 524 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-31.
Other instructions, from other repositories
ai-agent-rules-generator copilot.instructions.md
Glitch WooCommerce Payment Gateway plugin coding guidelines — auto-doc sync for plugin, features, and infrastructure.
ai-agent-rules-generator agent-observations.instructions.md
Mandatory agent observation logging — anomalies, recommendations, and critical findings must be disclosed before commit.
ai-agent-rules-generator task.instructions.md
Task execution rules for Glitch WooCommerce Payment Gateway engineering work.
ai-agent-rules-generator doc-sync.instructions.md
Documentation sync rules — which docs to update when code changes.
ai-agent-rules-generator browsetools.instructions.md
Browser verification rules for Glitch WooCommerce Payment Gateway using Chrome DevTools MCP.
ai-agent-rules-generator devtools.instructions.md
Browser DevTools and local development access credentials.