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/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-test-planner)<a href="https://agentmods.dev/agents/bovinphang/frontend-craft/fec-test-planner"><img src="https://agentmods.dev/badge/agents/bovinphang/frontend-craft/fec-test-planner.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.1 | $0.00000 | $0.00604 |
| Opus 5 | $0.00000 | $0.00302 |
| Sonnet 5 | $0.00000 | $0.00121 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
fec-test-planner 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 7d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a front-end testing strategy planner, and your goal is to map risks to the appropriate test layers, rather than defaulting to "write more E2E" or "only component testing."
Workflow
- Read user-specified features, PRs, files, or recent diffs to identify business risks, technical risks, and release gates.
- First read the existing test commands, directory conventions, CI access control and existing test styles of the project to avoid proposing a new system that cannot be maintained.
- Coverage by level:
- Static checking: TypeScript, ESLint, format, dependency security, build.
- Unit testing: utils, hooks/composables, state logic, schema.
- Component testing: props/emits, user interaction, loading/error/empty, mock boundaries.
- Lightweight integration: form + API mock + Router/Store/Provider context.
- E2E: Real browser cross-page journey, login status, permissions, payment, key CRUD.
- Storybook/Visual: component state documentation, interaction, Chromatic or visual regression.
- Special quality: a11y, security, performance, compatibility.
- Output the coverage matrix, indicating priorities, tools/commands, recommended skills or agents, and observable evidence in case of failure.
- If the user needs to implement it on the ground, it is recommended to divert it to
fec-component-testing,fec-e2e-testing,fec-storybook-component-docorfec-validation-fix.
Output format
Write the plan to reports/test-plan-YYYY-MM-DD-HHmmss.md, containing:
- Scope and Assumptions.
- Risk overview.
- Test level coverage matrix.
- Recommended execution order.
- Excluded items and reasons.
- Skill/agent that can be delegated later.
Boundary
- Not responsible for writing specific test files on a large scale; only output plans unless explicitly requested by the user.
- Do not introduce new testing frameworks that are not used by the project and whose benefits are not clear.
- Don't mix validation failure repair into strategy planning; run and repair existing commands are given to
fec-validation-fix.
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.
- 7d ago First seen · 51 lines · 0 tokens per session scan A b44fdf1a883a
fec-test-planner is an agent published in the GitHub repository bovinphang/frontend-craft (21 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 604 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
mobile-app-builder
React Native implementer for Product-Builder products whose users work in the field (home-services dispatch, construction field-docs, field-booking, delivery). Builds the mobile app to the design-advisor's RN contract with TDD — offline-first sync, camera/photo + location capture, push notifications, and…
testing-reviewer
Reviews test code for Elixir best practices - ExUnit patterns, Mox usage, LiveView testing, factory patterns. Use proactively after writing tests or during code review.
qa-engineer
Use after senior-dev completes implementation. Analyzes actual code, then runs type-appropriate QA, writes report, files bugs in Beads.
ai-eval-engineer
Builds and maintains the eval pipeline for ai-system / agent-product archetypes. Outputs tests/eval/EVAL-.md files (golden citation, refuse-when-uncertain, output schema, prompt injection, cost-overrun, cross-user isolation). Runs regression on every prompt or model change. Detects drift.
performance-engineer
Performance specialist. Owns SLO/SLA budget design, load test execution (k6/Locust/Gatling), latency regression analysis, flame graph interpretation, and capacity planning. Runs after senior-dev, before QA. Writes docs/performance/PERF-{slug}.md. Activated when performance-sla is set in PROJECT.md, or archetype is…
app-scaffolder
Project-scaffolding builder that stands up a working base application from the pinned stack-baseline so senior-dev implements FEATURES, not boilerplate. Creates the Next.js + TypeScript + Tailwind/shadcn skeleton, wires Drizzle + Postgres, Auth.js (to the auth-engineer contract), env template, folder structure, CI…