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-status)<a href="https://agentmods.dev/commands/rocky2431/ultra-builder-pro/ultra-status"><img src="https://agentmods.dev/badge/commands/rocky2431/ultra-builder-pro/ultra-status/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-status"><img src="https://agentmods.dev/badge/commands/rocky2431/ultra-builder-pro/ultra-status.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.00014 | $0.01113 |
| Opus 5 | $0.00007 | $0.00557 |
| Sonnet 5 | $0.00003 | $0.00223 |
| Haiku 4.5 | $0.00001 | $0.00111 |
Grade A, and why
ultra-status 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 11d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ultra-status
Purpose
Real-time project status monitoring with progress tracking, risk analysis, and actionable insights using native task system.
Workflow
Phase 0: Validation
Check environment before displaying status:
- Does
.ultra/tasks/tasks.jsonexist? → If not: Suggest/ultra-init(Chinese) - Are there tasks in the system? → If not: Suggest
/ultra-plan(Chinese) - Is task data valid? → Verify structure and timestamps
- Determine output format (quick vs full report)
Phase 1: Load Project Data
Read all status files:
.ultra/tasks/tasks.json- Task progress.ultra/test-report.json- Test status.ultra/delivery-report.json- Delivery status
Extract:
- Task statistics (total, by status, by priority)
- Current task (in_progress) and next pending task
- Test pass/fail status and run count
- Delivery readiness
Phase 2: Generate Progress Report
Display comprehensive project status:
- 📊 Overview: Progress bar, completion %, task velocity
- 📝 Tasks: By status (pending/in_progress/completed/blocked)
- 🧪 Test: Pass/fail, run count, blocking issues
- 📦 Delivery: Version, pushed status
- ⚠️ Risks: Auto-detected issues
- 📈 Next: Optimal next task
Phase 3: Analyze Risks
Auto-detect issues:
- Blockers: Tasks with unsatisfied dependencies
- Stalled tasks: In-progress >3 days
- Overdue: Past estimated completion
- Complexity spikes: Multiple complex tasks queued
- Resource constraints: Parallel task limits
Phase 4: Provide Recommendations
Suggest next optimal task based on:
- Priority (P0 > P1 > P2 > P3)
- Dependencies (only ready tasks)
- Complexity (balance with velocity)
- Context (similar to recent tasks)
Phase 5: Workflow Routing (▶ Next Up)
Detect workflow position from existing artifacts (no extra state file needed):
| Check | Condition | Route |
|---|---|---|
No .ultra/ dir |
Missing | → /ultra-init |
| No specs | product.md missing or has [NEEDS CLARIFICATION] |
→ /ultra-research |
| No tasks | tasks.json missing or empty |
→ /ultra-plan |
| Tasks pending | Any task status "pending" | → /ultra-dev (show which task) |
| All tasks done | All tasks "completed" | → /ultra-test |
| Test passed | test-report.json passed: true |
→ /ultra-deliver |
| Test failed | test-report.json passed: false |
→ /ultra-dev (show blocking issues) |
| Delivered | delivery-report.json exists |
→ Done. Suggest next milestone |
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.
- 11d ago First seen · 141 lines · 14 tokens per session scan A 23ab946e14c7
ultra-status is a command published in the GitHub repository rocky2431/ultra-builder-pro (11 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 1,113 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
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.