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/xml-configgit clone --depth 1 https://github.com/zexion7873/copilot-settingWhat 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.00924 | $0.00924 |
| Opus 5 | $0.00462 | $0.00462 |
| Sonnet 5 | $0.00185 | $0.00185 |
| Haiku 4.5 | $0.00092 | $0.00092 |
Grade A, and why
copilot-setting xml-config.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 2d 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
XML Configuration Conventions
Conventions for Spring XML config (applicationContext*.xml), Hibernate hbm.xml mappings, and Maven POM files. Transaction management rules: instructions/spring-hibernate.instructions.md.
Spring XML
- One config file per concern (e.g.,
applicationContext-dao.xml,applicationContext-service.xml) - Bean IDs: camelCase, descriptive (
orderService,transactionManager) - Transaction:
<tx:advice>+<aop:config>on service layer — seeinstructions/spring-hibernate.instructions.md
Hibernate hbm.xml
hbm.xml mapping conventions (file-per-entity, root package, lazy/FK naming): see instructions/spring-hibernate.instructions.md.
Maven POM
- Pin all dependency versions — no ranges, no
SNAPSHOTin releases, no dynamicLATEST/RELEASEmarkers <dependencyManagement>for version centralization in multi-module- Scopes: test-only libraries (JUnit, Mockito) use
<scope>test</scope>; container-provided APIs (servlet, JSP) use<scope>provided</scope>— never bundle them into the WAR maven-compiler-pluginwithsource/target=1.8; pin every plugin version (unpinned plugins follow Maven defaults — non-reproducible builds)- Encoding:
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
web.xml
This stack bootstraps via web.xml (no servlet initializers — see instructions/spring-hibernate.instructions.md), so these conventions apply:
<web-app>version matches the container's servlet spec and the Spring 3.2 runtime — do not declare a newer spec than the container providesCharacterEncodingFilterset to UTF-8 and mapped first in the filter chain, before any filter that reads request parameters (ties into the JSP output-encoding story —instructions/jsp.instructions.md)- Context split:
ContextLoaderListenerloads the root context (services, DAOs);DispatcherServletloads only its own web context (controllers, view resolvers) — do not redefine the same bean in both OpenSessionInViewFilter(OSIV), if used, is configured here — seeinstructions/spring-hibernate.instructions.md
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.
- 2d ago First seen · 47 lines · 924 tokens per session scan A cdf589f00b96
copilot-setting xml-config.instructions.md is an instructions file published in the GitHub repository zexion7873/copilot-setting (1 stars, last pushed 29d ago), licensed MIT. It adds 924 tokens to every session, about $0.0046 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
apm python.instructions.md
Python development guidelines.
loadout go.instructions.md
Go Engineering Instructions (CLI + API, framework-agnostic).
specs-driven-development-spring-angular production-code.instructions.md
Production code guardrails — TDD discipline and Spring Boot 4 conventions.
loadout python.instructions.md
Python Engineering Instructions (CLI + API, framework-agnostic).
loadout typescript.instructions.md
TypeScript Engineering Instructions (CLI + API + UI, framework-agnostic).
loadout rust.instructions.md
Rust Engineering Instructions.