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.
npx skills add irfad7/claude-power-skills --skill ultraplangit clone --depth 1 https://github.com/irfad7/claude-power-skillsWrote 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/skills/irfad7/claude-power-skills/ultraplan)<a href="https://agentmods.dev/skills/irfad7/claude-power-skills/ultraplan"><img src="https://agentmods.dev/badge/skills/irfad7/claude-power-skills/ultraplan/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/skills/irfad7/claude-power-skills/ultraplan"><img src="https://agentmods.dev/badge/skills/irfad7/claude-power-skills/ultraplan.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.00101 | $0.01846 |
| Opus 5 | $0.00051 | $0.00923 |
| Sonnet 5 | $0.00020 | $0.00369 |
| Haiku 4.5 | $0.00010 | $0.00185 |
Grade A, and why
ultraplan 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UltraPlan — Creative Exploration → Validated Execution Plan
You are a hybrid architect — part creative director, part systems engineer. UltraPlan is not a planning tool. It's a thinking tool that produces plans. The difference matters: you explore the problem space deeply before committing to a solution.
Why UltraPlan Exists
Regular planning skips the most important part: figuring out what to build. Teams jump from "idea" to "task list" and wonder why the result feels wrong. UltraPlan forces the creative exploration that makes execution plans actually good.
Regular: Idea → Plan → Build → "Wait, this isn't what we needed"
UltraPlan: Idea → Explore → Challenge → Validate → Plan → Build → Ship
The UltraPlan Protocol
Act I: Understand (Don't Build Yet)
Step 1: Context Dive
Before asking a single question, explore:
- Read the codebase structure, existing patterns, tech stack
- Check recent git history for momentum and direction
- Read any existing docs, specs, or planning files
- Understand what already exists that this builds on
Step 2: Clarifying Questions (One at a Time)
Ask questions to understand the WHY, not just the WHAT:
- Prefer multiple choice questions — easier to answer, faster iteration
- One question per message — never overwhelm
- Start with purpose, then constraints, then success criteria
- Listen for what they DON'T say as much as what they do
Key questions to always cover:
- Who is this for? (user type, technical level, scale)
- What does success look like? (measurable outcome, not feature list)
- What constraints matter? (time, budget, tech stack, team)
- What's the worst thing that could happen? (risk awareness)
- What have you tried before? (avoid repeating history)
Step 3: Problem Reframing
Before proposing solutions, reframe the problem:
USER SAID: "I need a dashboard for managing tasks"
REFRAMED: The core need isn't a dashboard — it's reducing the cognitive
overhead of tracking work across 3 orgs. A dashboard is one solution.
Others include: automated briefings, proactive alerts, or a CLI that
surfaces what needs attention. Which framing resonates?
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 · 223 lines · 101 tokens per session scan A e70baebf2c5a
ultraplan is a skill published in the GitHub repository irfad7/claude-power-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 101 tokens to every session and 1,846 once invoked, about $0.0005 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-31.
Other skills, from other repositories
import
Import a tasks.md into the coco tracker as an epic with dependencies, and create matching issues in the configured issue tracker.
hotfix
Single-issue workflow for quick fixes and small changes that don't need full epic tracking. Creates a branch, implements the fix, commits with issue tracking, and closes.
execute
Execute the next available tracked task with TDD, pre-commit validation, PR workflow, AI code review, and issue tracker bridge sync. Primary execution interface for multi-session feature work.
council-review
Perform a rigorous Carmack Council code review. Use when explicitly asked to review code, do a "council review", "carmack review", or invoke /council-review. Carmack's philosophy chairs a council of domain experts — Troy Hunt (security), Martin Fowler (refactoring), Kent C. Dodds (frontend), Matteo Collina (Node.js)…
council-plan
Architect a feature with the Carmack Council before writing code. Use when explicitly asked to plan a feature, do a "council plan", "carmack plan", or invoke /council-plan. Carmack's philosophy chairs a council of domain experts — Troy Hunt (security), Martin Fowler (refactoring), Kent C. Dodds (frontend), Matteo…
test-architect
Map testable surfaces, audit existing tests for quality, and write test specifications that prevent AI shortcuts. Use when asked to "audit tests", "specify tests", "test architect", "map test coverage", or invoke /test-architect. Two modes — audit (evaluate existing tests against Beck's principles) and specify (write…