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-bug.template)<a href="https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/ui-bug.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/ui-bug.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.00631 |
| Opus 5 | $0.00000 | $0.00316 |
| Sonnet 5 | $0.00000 | $0.00126 |
| Haiku 4.5 | $0.00000 | $0.00063 |
Grade A, and why
ui-bug.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 — 69 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-bug — Codex Runtime
Investigate and fix a UI bug. Playwright MCP (browser screenshot/interaction) is unavailable in Codex.
What I Can Do Without Playwright MCP
- Read the source code of the affected component
- Analyze the bug based on your description
- Propose a fix with code changes
- Generate a test to reproduce and verify the fix
- Run the test via:
npx playwright test --grep "bug-description"
To Start
Describe the UI bug you're seeing (what component, what behavior, what's expected). I'll investigate the code and propose a fix.
For live browser screenshot debugging, use Claude Code CLI: /ui-bug
description: File a structured bug report for Neovim UI issues
Neovim UI Bug Report
Create a structured bug report for nvim-ccasp UI issues with automatic context gathering (layout snapshot, error logs, reproduction steps).
Usage
/ui-bug
/ui-bug "flyout doesn't close when pressing Esc"
/ui-bug --with-snapshot
Bug Report Template
The command generates a structured report containing:
- Summary - One-line description
- Environment - Neovim version, OS, terminal, ccasp version
- Steps to Reproduce - Numbered list of actions
- Expected Behavior - What should happen
- Actual Behavior - What happens instead
- Layout Snapshot - Auto-captured window state at time of bug
- Error Log - Any Lua errors from vim.v.errmsg or :messages
- Affected Files - Which Lua modules are likely involved
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 · 69 lines · 0 tokens per session scan A 461db00b930c
ui-bug.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 631 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.