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/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.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.01814 | $0.01814 |
| Opus 5 | $0.00907 | $0.00907 |
| Sonnet 5 | $0.00363 | $0.00363 |
| Haiku 4.5 | $0.00181 | $0.00181 |
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 yesterday.
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 — 133 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/
Build & Validation
# Full validation suite
npm run validate:all
# Individual checks (most-used)
npm run lint:md # Markdown linting
npm run lint:json # JSON/JSONC validation
npm run validate:agents # Agent + prompt frontmatter, model alignment
npm run validate:agent-registry # Registry shape (file path, model, step)
npm run validate:iac-security-baseline # TLS/HTTPS/Entra-only/no-public-blob baseline
npm run lint:safe-shell # No interactive shell prompts in committed snippets
# Full list (≈30 scripts) → npm run | grep -E "^ (lint|validate|test):" or
# https://apexops.pro/reference/validation-reference/
# Pre-commit/pre-push hooks (installed via lefthook on `npm run prepare`)
git push # Triggers diff-based-push-check.sh automatically
# IaC validation
bicep build infra/bicep/{project}/main.bicep && bicep lint infra/bicep/{project}/main.bicep
terraform fmt -check -recursive infra/terraform/ && npm run validate:terraform
Code Style
Code style (CAF naming, required tags, default region, AVM-first, unique suffix pattern) is documented in .github/skills/azure-defaults/SKILL.md. Agents read that file as part of their mandatory skill load; this file no longer duplicates the tables.
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.
- yesterday 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 3d ago), licensed MIT. It adds 1,814 tokens to every session, about $0.0091 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-09-03.
Other instructions, from other repositories
frootai waf-operational-excellence.instructions.md
Operational excellence patterns — CI/CD, observability, IaC, incident management, and deployment automation aligned to Azure Well-Architected Framework.
apm cicd.instructions.md
CI/CD Pipeline configuration for PyInstaller binary packaging and release workflow.
PlatformPlatform AGENTS.md
Instructions for platformplatform/PlatformPlatform, covering behavioral guidelines, build, test, and format, product management tool, auto memory and source of truth.
rosetta db-meta-stamping.instructions.md
Released databases carry dbmeta provenance stamped in CI and surfaced by runtime entrypoints.
github-copilot-rules testing-xunit.instructions.md
This file provides guidelines for writing effective, maintainable tests using xUnit and related tools.
copilot-brag-sheet AGENTS.md
AGENTS.md instructions for microsoft/copilot-brag-sheet, covering agents.md, 1. project overview, 2. architecture map, 3. build / test / lint commands and run a single test file.