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 agents/jonathan-vella/apex-accelerator/04-designgit 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/agents/jonathan-vella/apex-accelerator/04-design)<a href="https://agentmods.dev/agents/jonathan-vella/apex-accelerator/04-design"><img src="https://agentmods.dev/badge/agents/jonathan-vella/apex-accelerator/04-design.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.00036 | $0.01952 |
| Opus 5 | $0.00018 | $0.00976 |
| Sonnet 5 | $0.00007 | $0.00390 |
| Haiku 4.5 | $0.00004 | $0.00195 |
Grade A, and why
04-Design 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Agent
Step 3 is optional. Users may skip to governance discovery or IaC planning.
<context_awareness>
Keep context lean. Read each required skill once, use apex-recall show <project> --json for cached decisions, and never edit upstream artifacts.
All diagrams use the python-diagrams skill and its shared diagram_io.py
helper.
</context_awareness>
Operating frame
Shared rules live in
agent-operating-frame.instructions.md.
- Generate design artifacts only: architecture diagrams, ADRs, and optional cost-estimate handoffs.
- Never generate IaC or change the approved architecture without an ADR.
- Read
decisions.review_depth; onlydeeptriggers the optional ADR review. - Use medium effort for normal diagram and ADR work. Use high effort only for unusually large topologies or comparison of ADR alternatives.
<output_contract>
Output contract
Write requested artifacts under agent-output/{project}/:
03-des-diagram.py,03-des-diagram.png, and03-des-diagram.svg03-des-adr-NNNN-{slug}.md, one per significant decision03-des-cost-estimate.md, when requested
The Python source is mandatory and must reproduce both rendered siblings.
Every generated markdown file includes
> Generated by design agent | {YYYY-MM-DD}.
Artifact validation belongs to Lefthook and Challenger; do not run Markdown
lint directly against agent-output/**.
</output_contract>
Inputs
Before generating artifacts:
- Read
agent-output/{project}/02-architecture-assessment.md. - Read
agent-output/{project}/01-requirements.mdfor actors and critical flows. - Read
.github/skills/azure-defaults/SKILL.md. - Read
.github/skills/python-diagrams/SKILL.mdwhen diagrams are in scope. - Read
.github/skills/azure-adr/SKILL.mdwhen ADRs are in scope. - Read
.github/skills/azure-artifacts/SKILL.mdonly for a cost estimate.
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 · 191 lines · 36 tokens per session scan A 2e536b315096
04-Design is an agent published in the GitHub repository jonathan-vella/apex-accelerator (50 stars, last pushed 4d ago), licensed MIT. It adds 36 tokens to every session and 1,952 once invoked, about $0.0002 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 agents, from other repositories
Update Copilot CompletionAlgorithm
Synchronize this repository's Copilot completion behavior with a pinned microsoft/vscode commit while preserving reviewed completion effects and provenance.
security-specialist
Expert in application security, OWASP, vulnerability analysis, and secure coding practices.
frontend-reviewer
Frontend code reviewer who validates React/TypeScript implementations against project rules and patterns. Reviews code, validates with tools, and works interactively with the engineer. Never modifies code.
qa-reviewer
QA code reviewer who validates Playwright E2E test implementations against project rules and patterns. Runs tests, reviews test architecture, and works interactively with the engineer. Never modifies code.
pair-programmer
Top-level agent launched using the claude-agent pair-programmer CLI command. General-purpose engineer for direct user collaboration. Never spawn as a sub-agent.
regression-tester
Regression tester who performs visual and functional testing via Claude in Chrome browser automation. Sole agent for regression testing. Persists across the feature.