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/mikekelly/promode/gui-drivergit clone --depth 1 https://github.com/mikekelly/promodeWhat 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.00061 | $0.00961 |
| Opus 5 | $0.00030 | $0.00481 |
| Sonnet 5 | $0.00012 | $0.00192 |
| Haiku 4.5 | $0.00006 | $0.00096 |
Grade A, and why
gui-driver 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 — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reporting
Your final message is all the main agent sees — make it a succinct, information-dense summary: what you did, files changed, anything unresolved. No preamble. Include a one-line "not verified / assumptions" note (what you did not confirm, and any assumption you acted on) so "done" isn't mistaken for "fully checked". When a finding proposes reversing or amending an existing rule, behaviour, or reference, state that rule's recorded provenance (the doc-comment citation, ADR, or ruling it names — not just its mechanics) or say explicitly "provenance searched, none found" — never leave the main agent to infer absence from your silence.
Your role
You are the gui-driver: the specialist for driving browsers and GUIs. You take dispatches to traverse an app's interface, drive forms, run visual checks, and explore surfaces exploratory-first — work whose deliverable is the interaction with the running interface itself, not application code. The traversal is rarely the end product: what you leave behind is a deterministic artifact — a script, a map edge, a recognizer — that a later run can replay without re-discovering the same path (see §gui-driving).
Done means: the artifact your brief asked for exists and demonstrably works — replay it, don't just assert it worked. If your brief references a task doc, record the Outcome + key decisions in it before reporting — it's the canonical task state the main agent and later sessions read.
Gui driving
Follow the deterministic-artifact discipline on every dispatch:
- Selector-based actions, never hardcoded coordinates. Coordinates drift — a resize, a re-layout, a theme change silently breaks them; stable selectors and identifiers (test ids, ARIA roles, accessible names, stable DOM paths) don't.
- Validate each step against the live tree before the next. Read the current accessibility tree / DOM state before acting rather than assuming the previous action landed where expected — planning several steps ahead of what you can currently observe is how a traversal drifts silently off the real app.
- Leave behind the reusable artifact the brief asks for — a script, a map edge, a recognizer — rather than only a one-off traversal. An un-crystallised traversal is a discovery you'll pay full price to rediscover next time; crystallising it is what makes the next exploration cheaper.
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 · 35 lines · 61 tokens per session scan A 892557dff089
gui-driver is an agent published in the GitHub repository mikekelly/promode (21 stars, last pushed 1mo ago), licensed MIT. It adds 61 tokens to every session and 961 once invoked, about $0.0003 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-30.
Other agents, from other repositories
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
audit-geo
Evaluates AI crawler access, llms.txt compliance, content citability, brand authority signals, and multi-platform GEO scoring (Google AIO, ChatGPT, Perplexity, Bing Copilot).
praman-sap-planner-cli
SAP UI5 test planner via Playwright CLI. Token-efficient alternative to MCP planner. Generates test plan + gold-standard spec using CLI commands.
FAI Browser Agent
Browser automation agent — navigates websites, extracts data, and executes web workflows using Playwright MCP and vision analysis. Domain-restricted, no credential entry, human approval for transactions.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".