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/rocky2431/ultra-builder-proWrote 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/rocky2431/ultra-builder-pro/ultra-test)<a href="https://agentmods.dev/commands/rocky2431/ultra-builder-pro/ultra-test"><img src="https://agentmods.dev/badge/commands/rocky2431/ultra-builder-pro/ultra-test/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/rocky2431/ultra-builder-pro/ultra-test"><img src="https://agentmods.dev/badge/commands/rocky2431/ultra-builder-pro/ultra-test.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.00021 | $0.02077 |
| Opus 5 | $0.00010 | $0.01038 |
| Sonnet 5 | $0.00004 | $0.00415 |
| Haiku 4.5 | $0.00002 | $0.00208 |
Grade A, and why
ultra-test 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 10d 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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ultra-test
Workflow Tracking (MANDATORY)
On command start, create tasks for each major step using TaskCreate:
| Step | Subject | activeForm |
|---|---|---|
| 0 | Pre-Execution Check | Checking prerequisites... |
| 1 | Anti-Pattern Detection | Detecting anti-patterns... |
| 2 | Coverage Gap Analysis | Analyzing coverage gaps... |
| 3 | E2E Testing | Running E2E tests... |
| 4 | Performance Testing | Testing performance... |
| 5 | Security Audit | Auditing security... |
| 6 | Auto-Fix Loop | Auto-fixing issues... |
| 7 | Persist Results | Persisting results... |
Before each step: TaskUpdate → status: "in_progress"
After each step: TaskUpdate → status: "completed"
On context recovery: TaskList → resume from last incomplete step
Pre-delivery quality audit. Validates test health, coverage gaps, E2E functionality, performance, and security.
Note: This is NOT for running unit tests (that's /ultra-dev). This is for auditing overall project quality before /ultra-deliver.
Pre-Execution
- Detect project type from config files (package.json, Cargo.toml, go.mod, pyproject.toml, etc.)
- Verify at least one task completed in
.ultra/tasks/tasks.json - Verify test files exist
Workflow
Step 1: Anti-Pattern Detection
Purpose: Detect fake/meaningless tests before they waste CI time.
What to detect:
- Tautology: Assertions that always pass (e.g.,
assert True,expect(true).toBe(true)) - Empty test: Test functions with no logic inside
- Core logic mock: Mocking domain/core/services code (violates test authenticity)
How:
- Identify test file patterns for detected language
- Construct appropriate regex for each anti-pattern
- Use Grep to scan and count matches
Result:
- 🟡 REPORTED (was BLOCKED): Any critical anti-pattern found
- ⚠️ WARNING: Minor issues found
- ✅ PASS: No anti-patterns
Step 2: Coverage Gap Analysis
Purpose: Find exported functions/classes not referenced in any test file.
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.
- 10d ago First seen · 255 lines · 21 tokens per session scan A 5b649599b8a5
ultra-test is a command published in the GitHub repository rocky2431/ultra-builder-pro (11 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 2,077 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
playwright-test-heal
Run all my tests and fix the failing ones.
paul:verify
Guide manual user acceptance testing of recently built features.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
ui-snapshot.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
laravel-playwright
E2E Playwright patterns; use the laravel:e2e-playwright skill exactly as written.
qa
Smoke or browser-walk a running app. Report only. Do not implement. Do not merge.