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-init)<a href="https://agentmods.dev/commands/rocky2431/ultra-builder-pro/ultra-init"><img src="https://agentmods.dev/badge/commands/rocky2431/ultra-builder-pro/ultra-init/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-init"><img src="https://agentmods.dev/badge/commands/rocky2431/ultra-builder-pro/ultra-init.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.00015 | $0.03257 |
| Opus 5.5 | $0.00006 | $0.01303 |
| Sonnet 5.5 | $0.00003 | $0.00651 |
| Haiku 4.5 | $0.00002 | $0.00326 |
Grade A, and why
ultra-init 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 2mo 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 — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ultra-init
Workflow Tracking (MANDATORY)
On command start, create tasks for each major step using TaskCreate:
| Step | Subject | activeForm |
|---|---|---|
| 1 | Collect Project Information | Collecting project info... |
| 1.5 | Interactive Confirmation | Confirming with user... |
| 2 | Create Project Structure | Creating .ultra/ structure... |
| 3 | Initialize Task System | Initializing tasks.json... |
| 4 | Copy Template Files | Copying templates... |
| 5 | Git Integration | Setting up Git... |
| 6 | Display Summary | Generating summary... |
Before each step: TaskUpdate → status: "in_progress"
After each step: TaskUpdate → status: "completed"
On context recovery: TaskList → resume from last incomplete step
Purpose
Initialize Ultra Builder Pro 6.8.0 project structure with native task management.
Arguments
$1: Project name (if empty, use current directory name)$2: Project type (web/api/cli/fullstack/other, if empty, auto-detect from dependencies)$3: Tech stack (if empty, auto-detect from package files)$4: "git" to initialize git repo (optional)
Pre-Execution Checks
Phase 0: Project State Detection
Detect project context before initialization:
-
Check existing
.ultra/directory- If exists → Trigger re-initialization flow
- Read existing config for comparison
-
Detect project code files
- Look for language-specific config files (package.json, Cargo.toml, go.mod, pyproject.toml, etc.)
-
Detect Git repository
- Check if
.git/directory exists - Use in interactive confirmation (show different Git options based on detection)
- Check if
-
Auto-detect project type and tech stack
- Analyze dependencies and config to identify frameworks, testing tools, and build systems
-
Use detection results in interactive confirmation
- Show detected values with labels
Triggers interactive confirmation for:
- Existing projects with code files
- Re-initialization scenarios
- Optional:
--interactiveflag
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.
- 2mo ago First seen · 318 lines · 15 tokens per session scan A d2416bc93910
ultra-init is a command published in the GitHub repository rocky2431/ultra-builder-pro (11 stars, last pushed 3mo ago), licensed MIT. It adds 15 tokens to every session and 3,257 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.
ultra-init compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| ultra-initrocky2431/ultra-builder-pro | Command | 11 | 3mo ago | MIT | A | 15 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |