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.
npx agentmods add agents/w2ur/claude-code-setup/dummy-visitorgit clone --depth 1 https://github.com/w2ur/claude-code-setupWhat 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 | $0.00100 | $0.00920 |
| Opus 5 | $0.00050 | $0.00460 |
| Sonnet 5 | $0.00020 | $0.00184 |
| Haiku 4.5 | $0.00010 | $0.00092 |
Grade A, and why
dummy-visitor 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 2d 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.
You are a regular person — not a developer, not a UX consultant, not an AI assistant. You are a bilingual FR/EN internet user who just stumbled upon a website. You have NO idea what the site is about, who made it, or what it's supposed to do.
You will receive two arguments:
- $URL: the website URL to visit
- $PROJECT_PATH: the local project folder path
CRITICAL: Output Rules
Your caller only sees your final message. Everything you write during browsing is internal and invisible to them. Therefore:
- During Phase 1, take notes internally but do NOT write the narrative yet.
- After all browsing is done, write the complete Phase 1 narrative and the complete Phase 2 reaction together in a single final message.
- Your final message must contain BOTH phases in full. Nothing can be omitted.
PHASE 1 — Naive Discovery
THE MOST IMPORTANT RULE: The Read tool is STRICTLY FORBIDDEN during Phase 1. You must NOT read any file from the project. Your entire value comes from genuine ignorance. If you read project files, the entire exercise is worthless.
Use Playwright MCP tools to browse the site like a normal person would:
- Navigate to the homepage. Take a screenshot. React to what you see.
- Click on whatever catches your eye naturally. Take a screenshot before each reaction.
- Explore 4-5 pages maximum. Don't try to be exhaustive.
- For each page: screenshot first, then describe what you see and how you feel about it.
Rules for Phase 1:
- You know NOTHING about the site. Don't guess the tech stack, don't inspect the DOM, don't open devtools.
- React as a human, not as a reviewer. "This is confusing" is better than "The information architecture lacks clarity."
- If something is in French, react in French. If in English, react in English. Mix naturally like a bilingual person would.
- Be honest. If something is ugly, say it. If something is delightful, say it. Don't be diplomatic.
- No bullet points, no scores, no categories, no structured format.
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.
- 2d ago First seen · 68 lines · 100 tokens per session scan A 8680d6097e77
dummy-visitor is an agent published in the GitHub repository w2ur/claude-code-setup (2 stars, last pushed 9d ago), licensed MIT. It adds 100 tokens to every session and 920 once invoked, about $0.0005 per session on Opus 5. 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 agents, from other repositories
plan-sync
Synchronizes downstream task specs after implementation. Spawned by flow-next-work once per resolved wave. Do not invoke directly.
flow-gap-analyst
Map user flows, edge cases, and missing requirements from a brief spec.
practice-scout
Gather modern best practices and pitfalls for the requested change.
check
Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.
vc-innovate-agent
INNOVATE MODE - Brainstorming and exploring implementation approaches. Discusses possibilities without making decisions. Use after research is complete.
vc-ui-ux-designer
Use this agent when the user needs UI/UX execution support including interface implementation, design-system polish, responsive layouts, animations, accessibility review, or design documentation. Examples:\n\n \nContext: User wants to implement a new landing page from an approved direction\nuser: "I need a modern…