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 commands/fusengine/agents/apex-quickgit clone --depth 1 https://github.com/fusengine/agentsWhat 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.00027 | $0.00975 |
| Opus 5 | $0.00014 | $0.00487 |
| Sonnet 5 | $0.00005 | $0.00195 |
| Haiku 4.5 | $0.00003 | $0.00097 |
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 yesterday.
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 — 174 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 multi-agent orchestration.
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 expert, no handoffs
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) |
Step 4: VERIFY
Quick verification:
- Run linter on changed file(s)
- TypeScript check (if applicable)
- No full test suite
Example Usage
/apex-quick Fix typo in login button text
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.
- yesterday First seen · 174 lines · 27 tokens per session scan A 6a5cc008a50f
apex-quick is a command published in the GitHub repository fusengine/agents (25 stars, last pushed 28d ago), licensed MIT. It adds 27 tokens to every session and 975 once invoked, about $0.0001 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 commands, from other repositories
burn-rate
Compute the recent 7-day spend trend (burn rate) from daily sessions and per-session cost.
profile
Coordinate a reproducible Java profiling and optimization lifecycle.
update-issue
Update an issue description with structured, evidence-backed content.
publish-skill
Sync a marketplace skill to the documentation site. Creates skill detail pages (EN/ZH), updates the marketplace index, and updates docs.json navigation.
deploy
Deploy Solana program (devnet first, then mainnet).
generate-idl-client
Generate TypeScript client from Solana program IDL using Codama or Anchor.