Borrowing it
Nothing to install: this file belongs to iamadi11/mcp-ui-poc. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/iamadi11/mcp-ui-poc/main/.claude/commands/start.mdgit clone --depth 1 https://github.com/iamadi11/mcp-ui-pocWrote 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/iamadi11/mcp-ui-poc/start)<a href="https://agentmods.dev/commands/iamadi11/mcp-ui-poc/start"><img src="https://agentmods.dev/badge/commands/iamadi11/mcp-ui-poc/start.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.01866 |
| Opus 5 | $0.00000 | $0.00933 |
| Sonnet 5 | $0.00000 | $0.00373 |
| Haiku 4.5 | $0.00000 | $0.00187 |
Grade A, and why
start 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 6d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/start
Autonomous end-to-end cycle: discover and choose one feature → research → plan → implement → QA (automated + MCP browser manual testing) → brutal user critique → commit → deploy.
Always follow docs/AI_WORKFLOW.md (Research → Plan → Test definition → Implement → Tests & checks → Validate → Document → Instrument). Do not skip steps without a one-line rationale.
Source of truth
- The codebase is the source of truth for behavior, APIs, patterns, and what is actually shipped. Read and trace real code paths before deciding what to build.
README.md(andCLAUDE.md,docs/AI_WORKFLOW.md) supply product intent, structure overview, ports, and scripts — use them to understand what this project is supposed to do and how to run it.- If README and code disagree (endpoints, flows, folder layout), follow the code and note the doc drift only if you fix docs in scope.
Phase A — Project context, then auto-collect and pick a feature
Run this before writing implementation code.
A1 — Understand the project (codebase first, README second)
- Codebase (mandatory) — Establish how the app actually works:
- Entry points: e.g.
server/index.js,client/src/main.jsx,client/src/App.jsx(adjust if the repo differs). - Trace
server/routes, MCP-related modules, andclient/src/UI flow enough to describe the main user journey in plain language. - Use
explore-codebasewhen layout or dependencies are unclear; prefer scoped search underserver/andclient/perdocs/AI_WORKFLOW.md.
- Entry points: e.g.
- README + project docs — Read
README.mdfor feature list, API summary, ports, and install/run steps; skimCLAUDE.mdanddocs/AI_WORKFLOW.mdfor workflow and boundaries. - Synthesize — In your working notes, write a short “what this project does” paragraph grounded in code + README (not generic stack guesses). This is the lens for every later step.
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.
- 6d ago First seen · 113 lines · 0 tokens per session scan A 3e206e8a3dcd
start is a command published in the GitHub repository iamadi11/mcp-ui-poc (8 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,866 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-08-31.
Other commands, from other repositories
auto-browse
Auto-browse — learn, optimize, and graduate browser operations or web data-mining workflows.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
can-i-use
Check browser support for web platform features against the project's browser targets.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.
qa
Smoke or browser-walk a running app. Report only. Do not implement. Do not merge.
verify-pr
Verify a PR's frontend changes through browser automation.