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 davistroy/claude-marketplace --skill ultra-plangit clone --depth 1 https://github.com/davistroy/claude-marketplaceWrote 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/davistroy/claude-marketplace/ultra-plan)<a href="https://agentmods.dev/skills/davistroy/claude-marketplace/ultra-plan"><img src="https://agentmods.dev/badge/skills/davistroy/claude-marketplace/ultra-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/skills/davistroy/claude-marketplace/ultra-plan"><img src="https://agentmods.dev/badge/skills/davistroy/claude-marketplace/ultra-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.00052 | $0.04361 |
| Opus 5.5 | $0.00021 | $0.01744 |
| Sonnet 5.5 | $0.00010 | $0.00872 |
| Haiku 4.5 | $0.00005 | $0.00436 |
Grade A, and why
ultra-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 — 385 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ultra Plan
Build a detailed, architecturally sound implementation plan for the provided issues, changes, updates, or features. This is a rigid workflow -- follow every phase in order. Do not skip phases or combine them. Each phase produces a distinct deliverable that gates the next.
See also:
/create-planfor requirements-driven planning./plan-improvementsfor codebase analysis and improvement recommendations.
Inputs
The user provides one or more of:
- A bug list, feature request list, or change set
- A GitHub issue or PR with identified problems
- A review document or audit with findings
- Verbal description of needed changes
If the input is ambiguous or incomplete, ask clarifying questions before starting Phase 0.
Arguments
| Argument | Description |
|---|---|
| (none) | Default mode: run the full rigid workflow (Phases 0-5) |
--refresh |
Drift detection mode: compare existing plan against current code state (see below) |
Drift Detection Mode (--refresh)
When invoked with --refresh, ultra-plan skips the normal Phase 0-5 workflow and instead checks whether an existing plan still matches the codebase.
Prerequisites:
- IMPLEMENTATION_PLAN.md (or
--input <path>) must exist - If no plan file exists, report: "No implementation plan found. Run
/ultra-planto create one, or specify a path with--refresh --input <path>."
Workflow:
Step 1: Read the Plan
Read the plan file. Extract all work items with their:
- Files Affected (expected file paths)
- Acceptance Criteria (expected behaviors)
- Status (PENDING, IN_PROGRESS, COMPLETE)
Step 2: Check Each Item Against Code
For each work item (focus on COMPLETE items — they're most likely to drift):
- File existence: Do the listed files still exist? Were any renamed or deleted?
- Acceptance criteria: For COMPLETE items, do the acceptance criteria still hold? (Read the relevant code and check.)
- New code: Has code been added in the affected areas that the plan doesn't account for?
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 · 385 lines · 52 tokens per session scan A 8d1d89d3f003
ultra-plan is a skill published in the GitHub repository davistroy/claude-marketplace (5 stars, last pushed 18d ago), licensed MIT. It adds 52 tokens to every session and 4,361 once invoked, about $0.0002 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-09-04.
Other skills, from other repositories
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.
diagnosing-missing-recordings
Diagnoses why a session recording is missing or was not captured. Use when a user asks why a session has no replay, why recordings aren't appearing, or wants to troubleshoot session replay capture issues for a specific session ID or across their project. Covers SDK diagnostic signals, project settings, sampling…