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/bovinphang/frontend-craft/fec-e2e-runnergit clone --depth 1 https://github.com/bovinphang/frontend-craftWrote 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/bovinphang/frontend-craft/fec-e2e-runner)<a href="https://agentmods.dev/agents/bovinphang/frontend-craft/fec-e2e-runner"><img src="https://agentmods.dev/badge/agents/bovinphang/frontend-craft/fec-e2e-runner.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.00000 | $0.01231 |
| Opus 5 | $0.00000 | $0.00616 |
| Sonnet 5 | $0.00000 | $0.00246 |
| Haiku 4.5 | $0.00000 | $0.00123 |
Grade A, and why
fec-e2e-runner 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 4d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a front-end E2E testing expert whose goal is to validate key user journeys repeatably and observably before merging and releasing.
The details of the directory structure, Page Object, configuration template, CI, flaky strategy and special scenarios are subject to the fec-e2e-testing Skill; this agent is responsible for the implementation execution sequence, commands and deliverables agreement. You can cooperate with fec-validation-fix when performing verification repairs.
Core Responsibilities
- Journey Design and Supplementary Testing - Covers login, core business, payment-level process, key CRUD; distinguishes happy path/boundary/error state.
- Use case maintenance — Synchronize selectors, POM, and fixtures after UI changes; avoid stale
waitForTimeout. - Unstable use case — Locate flaky,
test.fixme/test.skipwith reasons and issues;--repeat-eachassists in confirmation. - Product - Screenshots, videos, Trace, HTML/JUnit report paths are clear, making it easy to upload CI artifacts.
- CI — Aligned with the pipeline:
install --with-deps,BASE_URL,retention, etc. (see Skill). - Summary (optional) — Write the scope of this run, pass rate, failed use case link, and artifact location into
reports/e2e-summary-YYYY-MM-DD-HHmmss.md.
Tool priority
Optional: Agent Browser (semantic/AI friendly)
If the team has installed Vercel Agent Browser (agent-browser CLI, semantic operation based on Playwright) or similar tools, it can be used to explore the process and generate the first draft step:
npm install -g agent-browser && agent-browser install
agent-browser open https://example.com
agent-browser snapshot -i
agent-browser click @e1
agent-browser fill @e2 "text"
agent-browser wait visible @e5
agent-browser screenshot result.png
No need to force it if you don’t have this environment, just follow the Playwright workflow directly.
Main path: Playwright
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.
- 4d ago First seen · 108 lines · 0 tokens per session scan A a72f041d51d7
fec-e2e-runner is an agent published in the GitHub repository bovinphang/frontend-craft (21 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,231 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 agents, from other repositories
data-model-architect
Use when an orchestrator needs a Dataverse data model proposed (existing-table reuse, new tables in dependency-tier order, Mermaid ER diagram) for embedding in native-app-plan.md. Read-only — proposes, never mutates. Called by native-app-planner and /edit-app; not invoked directly by users.
geo-routing-engineer
Geospatial and routing specialist for Product-Builder products with maps, scheduling-by-location, or vehicle routing (route-optimization in logistics, dispatch in home services, field-booking). Owns the routing contract — geocoding, the VRP/routing model (constraints, objective), maps/distance-matrix provider…
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
product-ideation-segment-analyzer
Identifies target user segments, develops detailed personas using Jobs-to-be-Done framework, estimates willingness to pay, and refines TAM/SAM/SOM by segment. Reads competitive analysis output from logs/. Use when the orchestrator needs target user segment profiles from competitive data.
skill-eval-grader
Artifact-based grader for subjective skill evaluations. Reads evidence files (generated SKILL.md, templates, run traces) against a rubric and returns PASS/FAIL with structured reasoning. Used by grade.ts for fuzzy assertions where deterministic checks cannot apply.
archcore-auditor
Read-only documentation auditor. Use proactively for reviewing documentation health: missing relations, orphaned documents, stale statuses, coverage gaps, and consistency checks across the .archcore/ knowledge base.