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/intellegix/intellegix-code-agent-toolkitWrote 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/intellegix/intellegix-code-agent-toolkit/frontend-e2e)<a href="https://agentmods.dev/commands/intellegix/intellegix-code-agent-toolkit/frontend-e2e"><img src="https://agentmods.dev/badge/commands/intellegix/intellegix-code-agent-toolkit/frontend-e2e/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/intellegix/intellegix-code-agent-toolkit/frontend-e2e"><img src="https://agentmods.dev/badge/commands/intellegix/intellegix-code-agent-toolkit/frontend-e2e.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.15617 |
| Opus 5.5 | $0.00000 | $0.06247 |
| Sonnet 5.5 | $0.00000 | $0.03123 |
| Haiku 4.5 | $0.00000 | $0.01562 |
Grade A, and why
frontend-e2e 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 — 1,175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/frontend-e2e — Comprehensive Frontend E2E Live Test
Perform a thorough live E2E test of a frontend web application using browser-bridge MCP tools. Tests every page, interactive element, form, navigation flow, responsive breakpoint, and accessibility rule through real browser interaction.
Architecture: Detect -> Crawl -> Universal -> A11y -> Visual/UX -> Navigation -> Responsive -> Interactive -> Performance -> Report. $0 cost, fully local via browser-bridge.
CRITICAL: Execute the full test silently. Only interact with the user in Step 0 (URL/env confirmation) and Step 0.5 (auth probe). Present the full report at the end.
IMPORTANT: Per-page error isolation is MANDATORY. Every page's test suite is wrapped in error handling — if any test fails or errors, mark it FAIL and continue to the next page/test. NEVER abort the full run because of a single page failure.
Input
$ARGUMENTS = URL [flags]
| Flag | Description | Default |
|---|---|---|
--focus <path> |
Test only pages matching this path prefix | all pages |
--skip-a11y |
Skip accessibility checks (Tier 1.5) | enabled |
--skip-responsive |
Skip responsive/breakpoint tests (Tier 3) | enabled |
--max-pages <n> |
Override default page cap | 20 |
--deep |
Set page cap to 50 instead of 20 | off |
--auth-cookie <name=value> |
Inject a session cookie before crawl | none |
--skip-visual |
Skip visual/UX quality checks (Tier 1.7) | enabled |
--skip-design |
Skip visual design quality checks (Tier 1.8) | enabled |
--allow-submit |
Allow form submission (localhost/staging only) | off |
Step 0: Detect Application — MANDATORY, SILENT
- Parse
$ARGUMENTSfor URL and flags - If no URL: probe common dev server ports (3000, 3001, 4200, 5173, 5174, 8000, 8080) via
mcp__browser-bridge__browser_navigatetohttp://localhost:{port}— use first that responds - If still no URL: STOP — "Provide a URL or start a local dev server"
- Call
mcp__browser-bridge__browser_get_tabsto verify browser-bridge connection. If fails: STOP — "Browser-bridge not connected. Check Chrome extension." - Production safety gate: If URL is NOT
localhost,127.0.0.1, or does NOT containstaging/dev/testin hostname:- Present warning: "This appears to be a production URL. Interactive tests (Tier 4) will NOT submit forms. Use
--allow-submitonly for test/staging environments." - Set internal flag
SAFE_MODE = true(no form submissions, no button clicks that trigger navigation away)
- Present warning: "This appears to be a production URL. Interactive tests (Tier 4) will NOT submit forms. Use
- Navigate to URL via
mcp__browser-bridge__browser_navigate - Wait for page: try
mcp__browser-bridge__browser_wait_for_elementtargetingbody(timeout 15s). Known issue:wait_for_elementmay return "restricted URL" on localhost — if so, fall back tobrowser_evaluatewith!!document.bodycheck + 2s delay as workaround. - Take baseline screenshot via
mcp__browser-bridge__browser_screenshot
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 · 1,175 lines · 0 tokens per session scan A 8a2dc5c5ee97
frontend-e2e is a command published in the GitHub repository intellegix/intellegix-code-agent-toolkit (57 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 15,617 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-08-30.
Other commands, from other repositories
qa-sweep
Full platform QA sweep — auto-discovers every page, tests every UI element via browser automation, creates GitHub issues for all findings.
qa-automation
Set up a comprehensive test automation strategy.
qa-e2e
End-to-End tests with Playwright or Cypress.
tester
Comprehensive testing with parallel execution capabilities.
e2e
Generate and run E2E tests with Playwright.
test-browser
Run browser tests on pages affected by current PR or branch.