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/docs-triggergit 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.00495 | $0.00495 |
| Opus 5 | $0.00247 | $0.00247 |
| Sonnet 5 | $0.00099 | $0.00099 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
apex-accelerator docs-trigger.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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Documentation on Code Change
Purpose
Detect when code changes require documentation updates. This instruction complements the existing documentation standards:
- docs.instructions.md — content principles, architecture tables
- markdown.instructions.md — formatting, line limits, validation
- docs-writer skill — full doc maintenance workflows
Trigger Conditions
Check if documentation updates are needed when any of these occur:
Always Trigger
- New features or capabilities are added
- Breaking changes are introduced
- Installation or setup procedures change
- CLI commands or scripts are added/modified
- Dependencies or requirements change
Check and Update If Applicable
- API endpoints, methods, or interfaces change
- Configuration options or environment variables are modified
- Code examples in documentation become outdated
- Agent or skill definitions are added, renamed, or removed
- Bicep module structure changes (new modules, renamed parameters)
What to Update
README.md (root)
Update when:
- New agents or skills are added (update tables and counts)
- Project structure changes (update tree diagram)
- New capabilities are introduced (update feature list)
CHANGELOG.md
Update when:
- Any user-facing change is made (follow Keep a Changelog format)
- Use conventional commit type to determine section (Added, Changed, Fixed, Removed, Deprecated, Security)
Site docs (site/src/content/docs/)
Update when:
- Agents or skills are added, renamed, or removed
- Agent capabilities change significantly
- New documentation files are added
docs-writer References
Update when:
- Instruction files are added or removed
(
references/repo-architecture.md— instruction table and count) - Agent or skill inventory changes
(
references/freshness-checklist.md— expected counts)
Verification
After updating documentation:
- Run
npm run lint:md— zero errors required - Run
npm run lint:docs-freshness— zero findings required - Verify all relative links resolve to existing files
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 · 79 lines · 495 tokens per session scan A f69dad611a1b
apex-accelerator docs-trigger.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 495 tokens to every session, about $0.0025 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.