Borrowing it
Nothing to install: this file belongs to jonathan-vella/apex-accelerator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jonathan-vella/apex-accelerator/main/AGENTS.mdgit 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/agents-md)<a href="https://agentmods.dev/instructions/jonathan-vella/apex-accelerator/agents-md"><img src="https://agentmods.dev/badge/instructions/jonathan-vella/apex-accelerator/agents-md/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/jonathan-vella/apex-accelerator/agents-md"><img src="https://agentmods.dev/badge/instructions/jonathan-vella/apex-accelerator/agents-md.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.02448 | $0.02448 |
| Opus 5.5 | $0.00979 | $0.00979 |
| Sonnet 5.5 | $0.00490 | $0.00490 |
| Haiku 4.5 | $0.00245 | $0.00245 |
Grade A, and why
apex-accelerator AGENTS.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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
APEX
Setup Commands
# Clone the Accelerator template and open in dev container
# https://github.com/jonathan-vella/apex-accelerator
git clone https://github.com/YOUR-USERNAME/my-infraops-project.git && cd my-infraops-project
code . # then: F1 → Dev Containers: Reopen in Container
npm install # Node.js deps (validators, linting)
npm run setup # Azure + GitHub OIDC/secrets/RBAC
Python deps (diagrams and apex-recall) install automatically via the dev container's
post-create.sh. Setup details: https://apexops.pro/getting-started/azure-setup/
Install only versions whose upstream artifacts are at least seven days old, through CFS-approved sources.
Microsoft maintainers keep package managers on packagefeedproxy.microsoft.io for corporate laptops/dev boxes, or an
approved team-owned Azure Artifacts feed, and opt the dev container in with APEX_NPM_REGISTRY_HOST_PATH and
APEX_PIP_INDEX_HOST_PATH; the dev container uses public registries otherwise. Automated builds and CI require an
authenticated CFS-compliant feed.
Standing exception (history in #794, closed as not planned): no
authenticated CI feed exists and none is planned, so hosted CI does not meet this requirement. Every hosted job,
including the dev container validation job, installs from the public registries (no workflow configures a feed or sets
the opt-in variables). The exception does not extend to dev boxes or local builds.
Never bypass quarantine using public registries or ms-feed-* browsing URLs. Verify age and feed availability
before changing pins; missing versions or metadata are not permission to bypass these requirements.
These CFS and quarantine rules are Microsoft's supply-chain policy for its own maintainers' environments. Other users
and organizations apply their own equivalent controls and can point the dev container at their own sources; see
Package Sources.
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 Changed · -9 lines · -132 tokens per session 9a9caa7c9803
- 6d ago Changed · +5 lines · +67 tokens per session 21031dd48fec
- 16d ago Changed · +4 lines · +79 tokens per session 4f10c2348045
- 1mo ago Changed · +36 lines · +620 tokens per session 62fb8cc5491b
- 1mo ago First seen · 133 lines · 1,814 tokens per session scan A df01931d5b2d
apex-accelerator AGENTS.md is an instructions file published in the GitHub repository jonathan-vella/apex-accelerator (50 stars, last pushed yesterday), licensed MIT. It adds 2,448 tokens to every session, about $0.0098 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-09-03.
Other instructions, from other repositories
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.