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/jonathan-vella/apex-accelerator/copilot-instructionsgit clone --depth 1 https://github.com/jonathan-vella/apex-acceleratorWrote 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/jonathan-vella/apex-accelerator/copilot-instructions)<a href="https://agentmods.dev/instructions/jonathan-vella/apex-accelerator/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/jonathan-vella/apex-accelerator/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.01889 | $0.01889 |
| Opus 5 | $0.00945 | $0.00945 |
| Sonnet 5 | $0.00378 | $0.00378 |
| Haiku 4.5 | $0.00189 | $0.00189 |
Grade A, and why
apex-accelerator 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 5d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
APEX - Copilot Instructions
VS Code Copilot-specific orchestration instructions. For general project conventions, build commands, and code style, see the root
AGENTS.md.
Azure Defaults (canonical)
This section is the canonical declaration of Azure infrastructure defaults.
Every skill, agent, and prompt must reference this section — never restate
the values inline. The IaC workflow, CAF naming guidance, AVM procedure,
and reference index live in
.github/skills/azure-defaults/SKILL.md.
Default Regions
| Service | Default Region | Reason |
|---|---|---|
| All resources | swedencentral |
EU GDPR-compliant |
| Static Web Apps | westeurope |
Not available in swedencentral |
| Failover | germanywestcentral |
EU paired alternative |
Required Tags (Azure Policy Enforced)
Tag schema is whatever live Azure Policy enforces in the target
subscription. Governance Discovery (Step 3.5) discovers the real
contract via discover.py and writes it to
04-governance-constraints.json (tag_contract.tags[],
tag_contract.source: "policy"); that always wins.
Greenfield fallback (no tag policy found at any inherited scope):
the APEX-standard 9-tag set — environment, owner, costcenter,
application, workload, sla, backup-policy, maint-window,
technical-contact — all lowercase. This mirrors the org-wide
resource-group tag-deny policy (every key must exist on the RG or the
deployment is denied). Citation + greenfield decision checklist:
azure-defaults/references/tag-strategy.md.
The PascalCase set (
Environment,ManagedBy,Project,Owner) is a deprecated convention retained only for backward compatibility on existing projects whose deployed resources already carry that casing. Do not propagate it to new projects.ManagedByandProjectare not part of the required contract —ManagedBymay still be emitted as an optional deploy-provenance marker.
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.
- 5d ago First seen · 163 lines · 1,889 tokens per session scan A 1797fd9524f0
apex-accelerator copilot-instructions.md is an instructions file published in the GitHub repository jonathan-vella/apex-accelerator (50 stars, last pushed 4d ago), licensed MIT. It adds 1,889 tokens to every session, about $0.0094 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
frootai waf-cost-optimization.instructions.md
Cost optimization patterns — model routing, token budgets, right-sizing, caching, and FinOps practices aligned to Azure Well-Architected Framework.
frootai waf-operational-excellence.instructions.md
Operational excellence patterns — CI/CD, observability, IaC, incident management, and deployment automation aligned to Azure Well-Architected Framework.
frootai waf-performance-efficiency.instructions.md
Performance efficiency patterns — caching, streaming, async processing, bundle optimization, and latency reduction aligned to Azure Well-Architected Framework.
az104-cert-buddy copilot-instructions.md
Instructions for timothywarner-org/az104-cert-buddy, covering copilot instructions, repository purpose, key locations, skill and agent conventions and mcp server ids.
az104-cert-buddy CLAUDE.md
Instructions for timothywarner-org/az104-cert-buddy, covering claude.md, repository purpose, architecture, skill discovery (critical gotcha) and cross-reference dependencies.
rails-instructions rails-deployment.instructions.md
Instructions for levifig/rails-instructions, covering rails deployment with kamal, core philosophy, kamal principles, configuration strategy and server prerequisites.