Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/evan043/claude-cli-advanced-starter-packnpx agentmods add commands/evan043/claude-cli-advanced-starter-pack/ui-snapshot.templateWrote 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-snapshot.template)<a href="https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/ui-snapshot.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/ui-snapshot.template/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/evan043/claude-cli-advanced-starter-pack/ui-snapshot.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/ui-snapshot.template.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.00000 | $0.00557 |
| Opus 5.5 | $0.00000 | $0.00223 |
| Sonnet 5.5 | $0.00000 | $0.00111 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade A, and why
ui-snapshot.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 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 — 78 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-snapshot — Codex Runtime
Capture UI snapshots for visual regression. Playwright MCP is unavailable in Codex.
Alternative: Update Playwright Snapshots via Shell
# Update all snapshots
npx playwright test --update-snapshots
# Update snapshots for specific test
npx playwright test tests/visual.spec.ts --update-snapshots
For live Playwright MCP snapshot capture, use Claude Code CLI: /ui-snapshot
description: Capture Neovim window layout snapshot for debugging
Neovim UI Layout Snapshot
Capture a complete snapshot of all Neovim windows (including floating window configs) for debugging and regression tracking.
Usage
/ui-snapshot
/ui-snapshot --json
/ui-snapshot --diff previous
Snapshot Contents
For every window:
- Window ID and buffer number
- Buffer name and filetype
- Is floating (true/false)
- Float config: row, col, width, height, zindex, border
- Window highlight settings
Plus global state:
- Editor dimensions (columns x lines)
- Active window and cursor position
- Appshell state (active section, flyout visible, rail visible)
- Session list with running status
Running
# Capture to file
./scripts/nvim-snapshot.ps1
# Output is saved to:
# nvim-ccasp/tests/artifacts/last-snapshot.txt (human readable)
# nvim-ccasp/tests/artifacts/last-snapshot.json (machine readable)
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 · 78 lines · 0 tokens per session scan A 2b7e042a7e97
ui-snapshot.template is a command published in the GitHub repository evan043/claude-cli-advanced-starter-pack (61 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 557 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
debug
Deep-dive artifact analysis for diagnosing E2E test failures.
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.
test-suite
Run comprehensive test suite with coverage analysis.
fix
Correction automatisee des bugs identifies par la QA Recette.
web-checklist
A checklist command for testing a website after a Git merge. It records checklist items in a file so progress can be viewed and individual checks can be marked complete.
hatch3r-bug-plan
Diagnose a complex incident -- reproduce the symptom, rank root-cause hypotheses, design the fix path, and emit regression coverage items as a board-ready investigation.