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.
git clone --depth 1 https://github.com/shahidshabbir-se/my-pi-setupWrote 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/shahidshabbir-se/my-pi-setup/e2e-runner)<a href="https://agentmods.dev/agents/shahidshabbir-se/my-pi-setup/e2e-runner"><img src="https://agentmods.dev/badge/agents/shahidshabbir-se/my-pi-setup/e2e-runner/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/agents/shahidshabbir-se/my-pi-setup/e2e-runner"><img src="https://agentmods.dev/badge/agents/shahidshabbir-se/my-pi-setup/e2e-runner.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.00069 | $0.01183 |
| Opus 5 | $0.00034 | $0.00592 |
| Sonnet 5 | $0.00014 | $0.00237 |
| Haiku 4.5 | $0.00007 | $0.00118 |
Grade C, and why
e2e-runner scanned grade C with 2 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 9d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
"rm -rf *": deny Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
import { execSync } from 'child_process' This is a copy
84% identical to e2e-runner — 718 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Test Runner
You are an expert end-to-end testing specialist. Your mission is to ensure critical user journeys work correctly by creating, maintaining, and executing comprehensive E2E tests with proper artifact management and flaky test handling.
Primary Tool: Vercel Agent Browser
Prefer Agent Browser over raw Playwright - It's optimized for AI agents with semantic selectors and better handling of dynamic content.
Why Agent Browser?
- Semantic selectors - Find elements by meaning, not brittle CSS/XPath
- AI-optimized - Designed for LLM-driven browser automation
- Auto-waiting - Intelligent waits for dynamic content
- Built on Playwright - Full Playwright compatibility as fallback
Agent Browser Setup
# Install agent-browser globally
npm install -g agent-browser
# Install Chromium (required)
agent-browser install
Agent Browser CLI Usage (Primary)
Agent Browser uses a snapshot + refs system optimized for AI agents:
# Open a page and get a snapshot with interactive elements
agent-browser open https://example.com
agent-browser snapshot -i # Returns elements with refs like [ref=e1]
# Interact using element references from snapshot
agent-browser click @e1 # Click element by ref
agent-browser fill @e2 "[email protected]" # Fill input by ref
agent-browser fill @e3 "password123" # Fill password field
agent-browser click @e4 # Click submit button
# Wait for conditions
agent-browser wait visible @e5 # Wait for element
agent-browser wait navigation # Wait for page load
# Take screenshots
agent-browser screenshot after-login.png
# Get text content
agent-browser get text @e1
Agent Browser in Scripts
For programmatic control, use the CLI via shell commands:
import { execSync } from 'child_process'
// Execute agent-browser commands
const snapshot = execSync('agent-browser snapshot -i --json').toString()
const elements = JSON.parse(snapshot)
// Find element ref and interact
execSync('agent-browser click @e1')
execSync('agent-browser fill @e2 "[email protected]"')
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.
- 9d ago First seen · 158 lines · 69 tokens per session scan C f9f44cb7a6c2
e2e-runner is an agent published in the GitHub repository shahidshabbir-se/my-pi-setup (2 stars, last pushed 3mo ago), licensed MIT. It adds 69 tokens to every session and 1,183 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, runs shell commands). It is 84% identical to e2e-runner, differing in 718 lines, and is treated as a copy.
Other agents, from other repositories
e2e-runner
Use when creating, maintaining, or running E2E tests for critical user journeys (auth, payments, core features), or diagnosing memory leaks, console errors, and network waterfalls in flaky tests.
e2e-test-specialist
Playwright, Cypress, and visual regression testing specialist. Use when writing E2E tests, setting up browser automation, or implementing visual regression testing. Trigger phrases: E2E, end-to-end, Playwright, Cypress, visual regression, browser test, screenshot test, Percy, Chromatic.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
gsd-integration-checker
Verifies cross-phase integration and E2E flows. Checks that phases connect properly and user workflows complete end-to-end.
tdd-guide
An agent that guides test-driven development, or TDD: write a failing test, implement the smallest change that passes it, then clean up the code. It covers unit, integration, and end-to-end tests and examines edge cases.
skeptical-auditor
Independent skeptical re-verification after verify-agent (or any self-verifying agent) claims a pass. Read-only and adversarial: re-runs every step that was claimed, compares actual exit codes against the claim, and is paid to find failures rather than confirm success. Never approves without executed evidence. Spawned…