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/evan043/claude-cli-advanced-starter-packWrote 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/evan043/claude-cli-advanced-starter-pack/ui-fix.template)<a href="https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/ui-fix.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/ui-fix.template.svg" alt="Measured on agentmods" 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.00000 | $0.00642 |
| Opus 5 | $0.00000 | $0.00321 |
| Sonnet 5 | $0.00000 | $0.00128 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
ui-fix.template 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 3d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Runtime Compatibility
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows:
AskUserQuestion=> ask the user directly in chat.WebSearch/WebFetch=> use available web tools (search_query,open,find) and cite links.Read/Write=> use shell/filesystem tools in this workspace.- Claude-only MCP calls (for example Playwright MCP names) => use available equivalents or clearly state fallback.
- Keep intent and output format identical; only adapt execution mechanics.
ui-fix — Codex Runtime
Fix a UI issue. Playwright MCP screenshot/browser tools are unavailable in Codex, but I can fix code directly.
Describe what needs to be fixed and I'll:
- Read the relevant component files
- Identify the issue
- Apply the fix
- Optionally generate a regression test
For live browser visual debugging, use Claude Code CLI: /ui-fix
description: Debug and fix Neovim UI issues with guided workflow
Neovim UI Fix
Guided workflow to debug and fix nvim-ccasp UI issues. Reads a bug report or test failure, locates the root cause in Lua code, applies the smallest fix, and re-runs tests to verify.
Usage
/ui-fix
/ui-fix "flyout doesn't close on Esc"
/ui-fix --from-test ui_smoke_spec
Workflow
- Understand - Read the bug report or test failure output
- Locate - Identify the Lua module and function involved
- Diagnose - Read the code, trace the logic, find the root cause
- Fix - Apply the smallest change that resolves the issue
- Verify - Run the specific test that failed (or smoke test)
- Report - Summarize what was wrong and what was changed
Fix Principles
- Smallest fix first - Don't refactor while fixing
- One bug, one change - Don't combine fixes
- Test before and after - Capture snapshot before fix, verify after
- Don't break other tests - Run full suite after fix
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.
- 3d ago First seen · 68 lines · 0 tokens per session scan A 76324cb88341
ui-fix.template is a command published in the GitHub repository evan043/claude-cli-advanced-starter-pack (61 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 642 tokens. 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-03.
Other commands, from other repositories
verify-loop
A command that repeatedly checks recent code changes and tries to fix failures, with a configurable retry limit. It can run code review, builds, tests, linting, and type checks according to the project language.
perf-audit
Performance audit for web applications.
scaffold
Scaffold project components from templates.
build-fix
A build-error fixing procedure for TypeScript projects. It runs the project build, groups and explains errors, applies fixes one at a time, and checks the build again.
responsiveness-check
Test responsive layout across viewport widths.
shadcn-ui
Install and configure shadcn/ui components.