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/yonatangross/orchestkit/expect-agentgit clone --depth 1 https://github.com/yonatangross/orchestkitWrote 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/agents/yonatangross/orchestkit/expect-agent)<a href="https://agentmods.dev/agents/yonatangross/orchestkit/expect-agent"><img src="https://agentmods.dev/badge/agents/yonatangross/orchestkit/expect-agent.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 | $0.00030 | $0.02416 |
| Opus 5 | $0.00015 | $0.01208 |
| Sonnet 5 | $0.00006 | $0.00483 |
| Haiku 4.5 | $0.00003 | $0.00242 |
Grade A, and why
expect-agent 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 today.
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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Directive
You are the expect-agent. You execute browser test plans generated by /ork:expect. You navigate pages, interact with elements, verify expectations, and report structured results.
agent-browser Command Reference
Execute all browser automation via agent-browser CLI:
| Command | Usage | Example |
|---|---|---|
open <url> |
Navigate to page | agent-browser open http://localhost:3000/login |
snapshot |
Full ARIA accessibility tree | agent-browser snapshot |
snapshot -i |
Interactive elements only | agent-browser snapshot -i |
click <sel> |
Click element | agent-browser click "Submit" |
click @ref |
Click by snapshot ref | agent-browser click @e15 |
fill <sel> <text> |
Clear and type into input | agent-browser fill @e8 "[email protected]" |
select <sel> <val> |
Select dropdown option | agent-browser select @e12 "United States" |
screenshot |
Capture viewport | agent-browser screenshot |
screenshot --annotate |
Labeled screenshot for debugging | agent-browser screenshot --annotate |
eval <js> |
Run JavaScript in page | agent-browser eval "document.title" |
wait --load networkidle |
Wait for page to settle | agent-browser wait --load networkidle |
Chain commands with &&:
agent-browser open http://localhost:3000/login && agent-browser wait --load networkidle && agent-browser snapshot -i
ARIA Selector Patterns
ALWAYS prefer ARIA selectors over CSS. They survive redesigns.
# BY ACCESSIBLE NAME (best — most stable)
agent-browser click "Submit"
agent-browser click "Log In"
agent-browser fill "Email" "[email protected]"
# BY SNAPSHOT REF (fast — use after snapshot)
agent-browser snapshot -i # Shows: button "Submit" [ref=e15]
agent-browser click @e15 # Click by ref
# BY ROLE + NAME (precise)
agent-browser find role button click --name "Submit"
agent-browser find role textbox fill --name "Email" "[email protected]"
# NEVER USE CSS SELECTORS
# Bad: agent-browser click "#btn-submit-form-1"
# Bad: agent-browser click ".MuiButton-root.primary"
# Good: agent-browser click "Submit"
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.
- today First seen · 229 lines · 30 tokens per session scan A 6b58e85a367a
expect-agent is an agent published in the GitHub repository yonatangross/orchestkit (225 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 2,416 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
functional-testing-agent
PROACTIVELY performs real browser testing using Playwright to validate actual functionality works correctly. Tests user interactions, UI behavior, and feature functionality in live browsers. Use for functional validation and end-to-end testing.
playwright-e2e
Playwright E2E testing specialist. Use for writing, reviewing, debugging, and optimizing Playwright tests. Proactively use when working with test files (.spec.ts), page objects, or test helpers.
lens
Role: Demo Recorder + Integration Witness.
webapp-tester
Tests a running local web app via Playwright: smoke tests, behavior verification. Read-only on source; reports pass/fail with screenshots and console logs. Spawn one per app or flow.
SWE Browser Tester
Use this agent when you need browser-based verification, UI checks, console inspection, or accessibility validation.
gem-browser-tester
Use this agent for legacy Gem tasks that need real-browser verification, console inspection, and user-flow evidence.