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/docsgit clone --depth 1 https://github.com/jonathan-vella/apex-acceleratorWhat 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.00965 | $0.00965 |
| Opus 5 | $0.00483 | $0.00483 |
| Sonnet 5 | $0.00193 | $0.00193 |
| Haiku 4.5 | $0.00097 | $0.00097 |
Grade A, and why
apex-accelerator docs.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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Standards
Instructions for creating and maintaining user-facing documentation in the site/src/content/docs/ folder.
Structure Requirements
File Header
Every doc file must start with:
# {Title}
> [Current Version](../../VERSION.md) | {One-line description}
Adjust the relative path depth based on folder nesting (../../../VERSION.md from
site/src/content/docs/, ../../../../VERSION.md from a subfolder).
Single H1 Rule
Each file has exactly ONE H1 heading (the title). Use H2+ for all other sections.
Link Style
- Use relative links for internal docs (example pattern:
Quickstart -> quickstart.md) - For root file references, increase
../depth based on folder nesting (for example:../VERSION.md,../../VERSION.md) - Use reference-style links for external URLs
- No broken links (validated in CI)
Current Architecture
See tools/registry/count-manifest.json for current agent, subagent, and skill counts.
See tools/registry/agent-registry.json for the agent role → file mapping.
See tools/registry/agent-registry.json for the agent role → file/model/skills mapping.
Prohibited References
Do NOT reference these removed agents/skills:
- Architecture diagrams → Use the
python-diagramsskill adr.agent.md→ Useazure-adrskilldocs.agent.md→ Useazure-artifactsskill oras-builtagentazure-workload-docsskill → Useazure-artifactsskillazure-deployment-preflightskill → Merged into deploy agentorchestration-helperskill → Deleted (absorbed into orchestrator)github-issues/github-pull-requestsskills → Usegithub-operationsgh-cliskill → Merged intogithub-operations_shared/directory → Useazure-defaults+azure-artifactsskills
Admonitions (Starlight asides)
Use Starlight's four built-in admonition types consistently. Pick the weakest type that communicates the urgency; escalate only when needed.
| Type | When to use | Syntax |
|---|---|---|
note |
Side information that aids understanding but isn't required | :::note … ::: |
tip |
Optional best practice or shortcut | :::tip … ::: |
caution |
Behaviour that can cause confusion, unexpected cost, or rework | :::caution … ::: |
danger |
Data loss, security regression, irreversible destructive action | :::danger … ::: |
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 · 109 lines · 965 tokens per session scan A f99b6cb9f064
apex-accelerator docs.instructions.md is an instructions file published in the GitHub repository jonathan-vella/apex-accelerator (50 stars, last pushed 5d ago), licensed MIT. It adds 965 tokens to every session, about $0.0048 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
claude-code-settings copilot-instructions.md
Instructions for feiskyer/claude-code-settings, covering claude.md, environment setup, required dependencies, configuration and skills.
squad copilot-instructions.md
Copilot instructions for bradygaster/squad, covering copilot coding agent — squad instructions, ⚠️ identity lock — read this first, 🚦 route before you act — generic copilot sessions, adversarial input handling and team context.
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.
PromptKit copilot-instructions.md
Instructions for microsoft/PromptKit, covering promptkit — copilot instructions, how to use this repository, what this repository is, architecture and component conventions.
agent-rules testing.instructions.md
Instructions for lirantal/agent-rules, covering testing guidelines for node.js applications, general testing principles, guiding principles, descriptive test naming (three-part structure) and structure tests by the aaa pattern.