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)<a href="https://agentmods.dev/commands/fusengine/agents/apex"><img src="https://agentmods.dev/badge/commands/fusengine/agents/apex/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"><img src="https://agentmods.dev/badge/commands/fusengine/agents/apex.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.00042 | $0.01590 |
| Opus 5.5 | $0.00017 | $0.00636 |
| Sonnet 5.5 | $0.00008 | $0.00318 |
| Haiku 4.5 | $0.00004 | $0.00159 |
Grade A, and why
apex 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
APEX: Analyze-Plan-Execute-eLicit-eXamine
Execute the comprehensive APEX methodology for professional-grade development.
Complete documentation: skills/apex-methodology/SKILL.md
Phase 1: ANALYZE (Deep Exploration)
Use explore-codebase to understand relevant parts of the system
Goals:
- Identify where changes need to be made
- Understand existing patterns and conventions
- Map dependencies and impacts
- Locate relevant tests
Deliverable: Exploration summary with affected components
Phase 2: PLAN (Strategic Design)
Use research-expert to validate approach against best practices
Goals:
- Design solution following project patterns
- Identify edge cases and error handling
- Plan test strategy
- Estimate impact and complexity
Deliverable: Implementation plan with step-by-step approach
Plan Format:
### Implementation Steps
1. [Component A]: [Required changes]
2. [Component B]: [Required changes]
3. [Tests]: [Test cases to add]
### Edge Cases
- [Case 1]: [Handling approach]
- [Case 2]: [Handling approach]
### Testing Strategy
- Unit tests: [What to test]
- Integration tests: [Scenarios]
- Manual testing: [Steps]
Phase 3: EXECUTE (Precise Implementation)
Implement the solution:
- Follow the plan step-by-step
- Maintain existing code style and patterns
- Add inline documentation for complex logic
- Create/update tests alongside code
Quality Standards:
- SOLID principles without exception
- DRY, KISS, YAGNI
- Every file within
FUSE_SOLID_MAX_LINES(the hook ceiling) - Separate types/interfaces
- Security validation (OWASP Top 10)
Phase 3.5: eLICIT (Self-Review) - NEW
Expert agent self-reviews and self-corrects before sniper validation
Modes:
--auto: Auto-select techniques based on code type (default)--manual: Present 5 techniques, user chooses--skip-elicit: Skip directly to eXamine
Workflow:
┌─────────────────────────────────────────────────────────┐
│ ELICIT (6 steps) │
│ │
│ Init → Analyze → Select → Apply → Correct → Report │
│ │
│ Expert applies elicitation techniques from 12 cats: │
│ - Security (7) - Performance (6) │
│ - Architecture (6) - Testing (6) │
│ - Documentation (6) - UX/a11y (6) │
│ - Data (6) - Concurrency (6) │
│ - Integration (7) - Observability (6) │
│ - Code Quality (7) - Maintainability (6) │
│ │
│ Total: 75 techniques │
└─────────────────────────────────────────────────────────┘
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 b5a46bccae19
- 1mo ago First seen · 208 lines · 42 tokens per session scan A 8cd0d3c1f5a9
apex is a command published in the GitHub repository fusengine/agents (31 stars, last pushed 3d ago), licensed MIT. It adds 42 tokens to every session and 1,590 once invoked, about $0.0002 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
benchmark
Compare per-instruction CU with the stored baseline to catch regressions.
test-zh
A command that generates Python unit tests with pytest, a tool for running tests and checking expected results.
sdlc-test
Phase 4 — Testing & Security. Spawns qa-manual-tester, automation-qa-engineer, appsec-engineer, penetration-tester, performance-engineer.
wp-test
Run PHPUnit, Jest, or wp-scripts test for the current WordPress project.
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.