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/Joncik91/ucaiWrote 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/joncik91/ucai/plan)<a href="https://agentmods.dev/commands/joncik91/ucai/plan"><img src="https://agentmods.dev/badge/commands/joncik91/ucai/plan/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/joncik91/ucai/plan"><img src="https://agentmods.dev/badge/commands/joncik91/ucai/plan.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.06721 |
| Opus 5.5 | $0.00006 | $0.02688 |
| Sonnet 5.5 | $0.00003 | $0.01344 |
| Haiku 4.5 | $0.00001 | $0.00672 |
Grade A, and why
plan 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 1mo 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 — 650 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planning
You are helping a developer plan before building. This command works at two levels:
- No arguments (
/plan): Define the project — vision, goals, and full requirements backlog - With arguments (
/plan <feature>): Create a feature FRD grounded in the project spec
Core Principles
- Spec-driven: Every piece of work traces back to a specification
- Research before requirements: Understand the codebase and domain first
- Parallel discovery: Launch multiple agents simultaneously for speed
- Approval before output: Never write files without user sign-off
- Track progress: Write and update
tasks/todo.mdto track phase completion
Skill Loading — MANDATORY
Before starting discovery phases, you MUST identify and load relevant skills. This is not optional.
- Always load
Skill(ucai:architect)— planning is architecture work - For feature-level planning, also load the domain skill:
Skill(ucai:backend),Skill(ucai:frontend), etc. - Apply the skill's guidance throughout all subsequent phases
You MUST load at least one skill before proceeding. State which skill(s) you loaded and why.
Phase 0: Route
Goal: Determine planning level.
Input: $ARGUMENTS
Decision:
- If
$ARGUMENTSis empty or whitespace → Project-Level Mode (Phases 1P–5P) - If
$ARGUMENTShas content → Feature-Level Mode (Phases 1F–5F)
Project-Level Mode
Use this mode when starting a new project or defining project scope for the first time.
Phase 1P: Understand the Project
Goal: Know what needs to be built.
Actions:
- Create todo list with all project-level phases (1P–6P)
- If
.claude/project.mdalready exists, read it and ask: "A project spec already exists. Overwrite, refine, or abort?" Wait for user decision. - If
.claude/requirements.mdalready exists, note this — it will be regenerated alongside the project spec. - Determine if this is greenfield (no source code) or brownfield (existing codebase):
- Use Glob to check for source files:
**/*.{js,ts,jsx,tsx,py,go,rs,java,rb,php,cs,cpp,c,swift,kt}
- Use Glob to check for source files:
- Ask the user:
- What are you building? (brief description)
- What problem does it solve? Who is the target user?
- Any known constraints? (tech stack preferences, deployment target, timeline)
- Classify project scale — this calibrates build order (Phase 5P) and milestone scoping (Phase 3F.5):
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.
- 1mo ago First seen · 650 lines · 14 tokens per session scan A a51f63927ab9
plan is a command published in the GitHub repository Joncik91/ucai (28 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 6,721 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.
Other commands, from other repositories
f5-gate
Quality gate management with evidence collection.
f5-classify
Classify input files by type using content-first analysis, detect gaps, and generate coverage declaration.
f5-implement
Implement features and fix bugs with traceability.
f5-import
Import documents - single, batch, analyze, or schema management.
f5-analytics
View project analytics and metrics.
f5-design
Generate design documents and specifications (D1-D4).