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/azure-artifactsgit 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/azure-artifacts)<a href="https://agentmods.dev/instructions/jonathan-vella/apex-accelerator/azure-artifacts"><img src="https://agentmods.dev/badge/instructions/jonathan-vella/apex-accelerator/azure-artifacts.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.1 | $0.02037 | $0.02037 |
| Opus 5 | $0.01019 | $0.01019 |
| Sonnet 5 | $0.00407 | $0.00407 |
| Haiku 4.5 | $0.00204 | $0.00204 |
Grade A, and why
apex-accelerator azure-artifacts.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 6d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Artifact Generation Rules
Use exact H2 headings from the template files. Violations block commits and PRs.
The artifact contract is enforced at commit/CI time only — agents do not
self-lint. Validated by the lefthook artifact-validation pre-commit hook
(which wraps npm run validate:artifacts) and CI; see
agent-authoring.instructions.md.
The azure-artifacts/SKILL.md is authoritative — read it for templates, workflow, styling.
Structural Elements (Beyond H2 Headings)
Templates define structural elements that agents reproduce.
Validated by the lefthook artifact-validation pre-commit hook (wraps
npm run validate:artifacts / lint:artifact-templates) and CI — agents do
not self-lint.
| Element | What to Copy from Template |
|---|---|
| Badge row | ![Step] / ![Status] / ![Agent] shields |
| Collapsible TOC | <details open> block with section links |
| Attribution | > Generated by {agent} agent | {date} |
| Cross-navigation | Header table with ⬅️ Previous / 📑 Index / Next ➡️ |
| Mermaid diagrams | ```mermaid blocks (keep or replace with real content) |
| Traffic-light status | Use ✅ / ⚠️ / ❌ in status columns (all three required) |
| Collapsible sections | <details> blocks for expandable content |
Complete H2 Heading Reference
Copy-paste headings from the template files. Do not paraphrase.
Canonical H2 heading lists for all 15 artifact types live in the template files:
| Artifacts | Template Reference |
|---|---|
| 01-requirements | references/01-requirements-template.md |
| 02-architecture, 03-cost-estimate | references/02-architecture-template.md |
| 04-plan, 04-governance, 04-preflight | references/04-plan-template.md |
| 05-implementation-reference | references/05-code-template.md |
| 06-deployment-summary | references/06-deploy-template.md |
| 07-* (all Step 7 docs) | references/07-docs-template.md |
project README (agent-output/<project>/README.md) |
references/PROJECT-README.template.md — H2 set is byte-exact incl. emoji: 📋 Project Summary, ✅ Workflow Progress, 🏛️ Architecture, 📄 Generated Artifacts, 🔗 Related Resources |
| sku-manifest | templates/sku-manifest.template.md + sku-manifest.instructions.md (authoritative; rendered from sku-manifest.json — schema-driven, not H2-sync-enforced) |
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.
- 6d ago First seen · 151 lines · 2,037 tokens per session scan A bfec61700a2c
apex-accelerator azure-artifacts.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 2,037 tokens to every session, about $0.0102 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.
ATV-Phoenix copilot-instructions.md
Copilot instructions for All-The-Vibes/ATV-Phoenix: Read AGENTS.md first. It is the binding build charter and it governs all work here.
is-ai-native copilot-instructions.md
Instructions for webmaxru/is-ai-native, a project described as: Audit public GitHub repositories for AI coding readiness across Copilot, Claude Code, and Codex.
claude-plugins CLAUDE.md
Instructions for peterblazejewicz/claude-plugins, covering claude.md, repository overview, plugin architecture, command files and plugin: avalonia-dev.
copilot-security-instructions mcp-server.development.instructions.md
Instructions for Robotti-io/copilot-security-instructions, covering mcp server development rules (this repo), core standards, express / http handling, mcp tools and logging hygiene.