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/bitflight-devops/skilllintWrote 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/bitflight-devops/skilllint/ultraplan-phase)<a href="https://agentmods.dev/commands/bitflight-devops/skilllint/ultraplan-phase"><img src="https://agentmods.dev/badge/commands/bitflight-devops/skilllint/ultraplan-phase/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/bitflight-devops/skilllint/ultraplan-phase"><img src="https://agentmods.dev/badge/commands/bitflight-devops/skilllint/ultraplan-phase.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.00030 | $0.00250 |
| Opus 5 | $0.00015 | $0.00125 |
| Sonnet 5 | $0.00006 | $0.00050 |
| Haiku 4.5 | $0.00003 | $0.00025 |
Grade A, and why
gsd:ultraplan-phase 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 8d 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.
This is a copy
86% identical to gsd-ultraplan-phase — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Ultraplan drafts the plan in a remote cloud session while your terminal stays free. Review and comment on the plan in your browser, then import it back via /gsd:import --from.
⚠ BETA: ultraplan is in research preview. Use /gsd:plan-phase for stable local planning. Requirements: Claude Code v2.1.91+, claude.ai account, GitHub repository.
<execution_context> @./.claude/get-shit-done/workflows/ultraplan-phase.md @./.claude/get-shit-done/references/ui-brand.md </execution_context>
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.
- 8d ago First seen · 35 lines · 30 tokens per session scan A 2f36e69b76e0
gsd:ultraplan-phase is a command published in the GitHub repository bitflight-devops/skilllint (7 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 250 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to gsd-ultraplan-phase, differing in 10 lines, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.