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/markdowngit 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/markdown)<a href="https://agentmods.dev/instructions/jonathan-vella/apex-accelerator/markdown"><img src="https://agentmods.dev/badge/instructions/jonathan-vella/apex-accelerator/markdown.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.00746 | $0.00746 |
| Opus 5 | $0.00373 | $0.00373 |
| Sonnet 5 | $0.00149 | $0.00149 |
| Haiku 4.5 | $0.00075 | $0.00075 |
Grade A, and why
apex-accelerator markdown.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 4d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Markdown Documentation Standards
Standards for creating consistent, accessible, and well-structured markdown documentation. Follow these guidelines to ensure documentation quality across the repository.
General Instructions
- ATX-style headings (
##,###) — never H1 in content - CRITICAL: 120-char line limit (CI + pre-commit enforced)
- Break at natural points; LF line endings
- Meaningful alt text for images; validate with
npm run lint:md
Line Length
120 chars max (CI enforced). Break after punctuation, before [, code block for long spans.
Content Structure
| Element | Rule | Example |
|---|---|---|
| Headings | Use ## for H2, ### for H3, avoid H4+ |
## Section Title |
| Lists | Use - for unordered, 1. for ordered |
- Item one |
| Code blocks | Use fenced blocks with language | ```bicep |
| Links | Descriptive text, valid URLs | [Azure docs](https://...) |
| Images | Include alt text |  |
| Tables | Align columns, include headers | See examples below |
Code Blocks
Specify language after backticks. Never bare fences.
Diagram Embeds
Use the appropriate diagram skill for each output type:
- Architecture diagrams →
python-diagramsskill (.py,.png,.svg) - WAF/cost/compliance charts →
python-diagramsskill (.py+.png) - Inline markdown diagrams →
mermaidskill (fenced code blocks)
Audience-specific guidance — for human-authored documentation in
site/src/content/docs/**anddocs/**, additional visual + template rules live inmarkdown-docs.instructions.md. For agent-generated artifacts inagent-output/**, H2 template compliance is enforced byazure-artifacts.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.
- 4d ago First seen · 72 lines · 746 tokens per session scan A 949d3cebc63d
apex-accelerator markdown.instructions.md is an instructions file published in the GitHub repository jonathan-vella/apex-accelerator (50 stars, last pushed 2d ago), licensed MIT. It adds 746 tokens to every session, about $0.0037 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
squad squad-routing-guard.instructions.md
Squad routing guard — explicit routing rules so the Copilot CLI routes tasks to the right Squad agent instead of handling them directly.
vscode-unify-chat-provider AGENTS.md
Instructions for smallmain/vscode-unify-chat-provider, a project described as: Integrate multiple LLM API providers into VS Code's GitHub Copilot Chat using the Language Model API. One-click use of your Claude Code, Gemini CLI, Antigravity, Github Copilot, OpenAI Codex (ChatGPT Plus/Pro), xAI Grok (SuperGrok / X…
PlatformPlatform AGENTS.md
Instructions for platformplatform/PlatformPlatform, covering behavioral guidelines, build, test, and format, product management tool, auto memory and source of truth.
copilot-instructions copilot-instructions.md
Instructions for SebastienDegodez/copilot-instructions, covering copilot instructions, language policy, development code generation and workflow implementation.
github-copilot-rules testing-xunit.instructions.md
This file provides guidelines for writing effective, maintainable tests using xUnit and related tools.
github-copilot-rules coding-guidelines.instructions.md
This file provides guidelines for writing clean, maintainable, and idiomatic C# code with a focus on functional patterns and proper abstraction.