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/PMDevSolutions/Aureliusnpx agentmods add commands/pmdevsolutions/aurelius/build-from-screenshotWrote 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/pmdevsolutions/aurelius/build-from-screenshot)<a href="https://agentmods.dev/commands/pmdevsolutions/aurelius/build-from-screenshot"><img src="https://agentmods.dev/badge/commands/pmdevsolutions/aurelius/build-from-screenshot/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/pmdevsolutions/aurelius/build-from-screenshot"><img src="https://agentmods.dev/badge/commands/pmdevsolutions/aurelius/build-from-screenshot.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.03355 |
| Opus 5.5 | $0.00000 | $0.01342 |
| Sonnet 5.5 | $0.00000 | $0.00671 |
| Haiku 4.5 | $0.00000 | $0.00335 |
Grade A, and why
build-from-screenshot 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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/build-from-screenshot — Autonomous Screenshot/URL-to-Working-App Pipeline
You are the master orchestrator for converting screenshots or a live URL into a fully working, tested application. You receive one or more image file paths OR a URL and guide the entire process through 12 phases, using specialized skills and agents. The output target (React, Vue, Svelte, React Native) is determined during intake and drives agent selection in the build phase.
Key enforcement rules:
- TDD is mandatory — Phase 3 (TDD) MUST complete before Phase 4 (Build). No exceptions.
- Visual QA uses pixel diff — Phase 5 uses
scripts/visual-diff.jsfor programmatic comparison, not manual eyeballing. - E2E tests are generated — Phase 6 generates and runs Playwright E2E tests appropriate to the app type.
- App-type aware — Chrome extensions, PWAs, and web apps each get tailored test strategies.
- Token inference requires confirmation — Phase 2 extracts tokens via AI vision and MUST get user confirmation before locking.
- Renderer-driven — Phase 4 dispatches the converter agent named by the resolved renderer manifest (
renderer-registry.js resolve <renderer>), not a hardcodedoutputTargettable.
Input
The user provides: $ARGUMENTS (a URL or one or more image file paths)
Detect input type:
- If
$ARGUMENTSstarts withhttp://orhttps://→ URL capture mode- The pipeline will navigate to the URL and capture screenshots automatically
- Store the original URL for the build report
- Otherwise → File paths mode
- Treat
$ARGUMENTSas one or more image file paths (space-separated or glob) - Verify each file exists before proceeding
- Treat
URL capture mode steps:
- Use Chrome DevTools MCP to navigate to the URL:
mcp__chrome-devtools__navigate_page - Resize to standard viewports (desktop 1440px, tablet 768px, mobile 375px):
mcp__chrome-devtools__resize_page - Take screenshots at each viewport:
mcp__chrome-devtools__take_screenshot - Save screenshots to
.claude/visual-qa/screenshots/source/
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 · 262 lines · 0 tokens per session scan A a102a3ce6b6e
build-from-screenshot is a command published in the GitHub repository PMDevSolutions/Aurelius (9 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,355 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-04.
Other commands, from other repositories
implement
E2E-first Test driven development — unit tests written last.
distill
Creates E2E acceptance tests in Given-When-Then format from requirements and architecture. Use when preparing executable specifications before implementation.
fix
Correction automatisee des bugs identifies par la QA Recette.
qa
Validate an application against a Gherkin user story by spawning a QA team that drives the running app.
test
Write tests before implementation using Red-Green-Refactor.
test-author
Write tests first (RED→GREEN→REFACTOR) with Vitest, Testing Library, and Playwright for a Next.js + Supabase app. Use when adding a feature, fixing a bug, or...