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.
git clone --depth 1 https://github.com/fusengine/agentsWrote 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/commands/fusengine/agents/apex-quick)<a href="https://agentmods.dev/commands/fusengine/agents/apex-quick"><img src="https://agentmods.dev/badge/commands/fusengine/agents/apex-quick/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/fusengine/agents/apex-quick"><img src="https://agentmods.dev/badge/commands/fusengine/agents/apex-quick.svg" alt="Reviewed on agentmods" width="80" 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.00027 | $0.01085 |
| Opus 5.5 | $0.00011 | $0.00434 |
| Sonnet 5.5 | $0.00005 | $0.00217 |
| Haiku 4.5 | $0.00003 | $0.00109 |
Grade A, and why
apex-quick 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 3d 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
APEX Quick Flow
Fast-track workflow for simple bug fixes, typos, and minor changes. No team, no handoffs between agents.
The main session never edits. It spawns ONE domain-expert agent (Agent with the Project Detection subagent_type, rule 01) with a self-contained brief; that agent locates, applies the minimal change, reviews and validates. The main session only briefs, verifies the result on disk, and runs sniper.
When to Use
✅ Use APEX Quick:
- Typo fixes
- Single-line bug fixes
- Simple refactoring (rename, move)
- Minor UI tweaks
- Config changes
- Documentation updates
❌ Use Full APEX instead:
- New features
- Multi-file changes
- Security-related code
- Database migrations
- API changes
Quick Flow Workflow
┌─────────────────────────────────────────────────────────┐
│ APEX QUICK (Single Pass) │
│ │
│ ┌─────────┐ ┌─────────┐ ┌─────────┐ ┌────────┐ │
│ │ LOCATE │ → │ FIX │ → │ REVIEW │ → │ VERIFY │ │
│ └─────────┘ └─────────┘ └─────────┘ └────────┘ │
│ │ │ │ │ │
│ ▼ ▼ ▼ ▼ │
│ Find file Apply 1 quick Linter │
│ + line minimal technique check │
│ change │
└─────────────────────────────────────────────────────────┘
Total: 4 steps, 1 delegated expert, no handoffs. Steps 1-4 are executed by the spawned expert, not by the main session.
Execution
Step 1: LOCATE
Expert does quick search:
- Grep for relevant code
- Read the file
- Identify exact location
Step 2: FIX
Expert applies minimal change:
- Only change what's necessary
- Preserve existing style
- No refactoring scope creep
Step 3: REVIEW (Auto-Elicit)
Expert applies 1 quick technique based on fix type:
| Fix Type | Quick Technique |
|----------|-----------------|
| Bug fix | TEST-01 (Edge cases) |
| Typo | DOC-03 (Consistency) |
| Style | MAINT-02 (Convention) |
| Security | SEC-02 (Validation) |
| Config | DATA-01 (Schema) |
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.
- 3d ago Changed · +2 lines 4c9f5cedd9f0
- 1mo ago First seen · 174 lines · 27 tokens per session scan A 6a5cc008a50f
apex-quick is a command published in the GitHub repository fusengine/agents (31 stars, last pushed 3d ago), licensed MIT. It adds 27 tokens to every session and 1,085 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.