agentmods.dev

feature-tests

feature-tests is an agent for Claude Code from VoxTechnologies/transmute-framework. It costs 244 tokens per session (1,849 once invoked), scanned A, original, MIT.

An end-to-end testing helper that writes Playwright tests for a feature. These tests check complete user flows through the running application, rather than testing one function or component alone.

In plain words
What is it for?
Use it to create Playwright tests for completed features, based on acceptance criteria, documented user flows, security requirements, and the project's testing rules.
Why use it?
It removes the need to manually turn feature requirements and user flows into browser-based tests. It also keeps end-to-end testing separate from backend function tests and frontend component tests.

Agent for Claude Code

Written for Claude Code: effort in frontmatter. Also seen: model in frontmatter; mentions CLAUDE.md.

Part of the transmuter plugin — 23 skills, 1 command, 7 agents, 2 hooks shipped together

not rated 5repo changed 16d ago A scan 244 tokens original MIT

Good fit Use it to create Playwright tests for completed features, based on acceptance criteria, documented user flows, security requirements, and the project's testing rules.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/voxtechnologies/transmute-framework/feature-tests
View source ↗ VoxTechnologies/transmute-framework transmuter.3mergen.com
Install

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.

Clone the repo
git clone --depth 1 https://github.com/VoxTechnologies/transmute-framework

Made for: Claude Code.

Or install transmuter, the plugin that ships this one along with the rest of its 23 skills, 1 command, 7 agents, 2 hooks.

Wrote 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.

agentmods badge for feature-tests

README.md
[![agentmods](https://agentmods.dev/badge/agents/voxtechnologies/transmute-framework/feature-tests/github.svg)](https://agentmods.dev/agents/voxtechnologies/transmute-framework/feature-tests)
Your own site
<a href="https://agentmods.dev/agents/voxtechnologies/transmute-framework/feature-tests"><img src="https://agentmods.dev/badge/agents/voxtechnologies/transmute-framework/feature-tests/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.

agentmods 80×15 button for feature-tests

Your own site · 80×15
<a href="https://agentmods.dev/agents/voxtechnologies/transmute-framework/feature-tests"><img src="https://agentmods.dev/badge/agents/voxtechnologies/transmute-framework/feature-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 244 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,849 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00244 $0.01849
Opus 5.5 $0.00098 $0.00740
Sonnet 5.5 $0.00049 $0.00370
Haiku 4.5 $0.00024 $0.00185

Measured 16d ago against content hash cc121cacd95b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

feature-tests 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 16d 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.

agents/feature-tests.md · 129 lines

How it starts

The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are an E2E Test Writing Teammate — responsible for writing Playwright end-to-end tests for a specific feature as part of the Transmute pipeline Stage 5.

Role

You write Playwright E2E tests for the feature assigned to you by the Feature Orchestrator (team lead). Backend function tests are the backend builder's responsibility. Component tests are the frontend builder's responsibility. Your scope is E2E tests only.

Before Writing Any Tests

  1. Read CLAUDE.md — Follow all Part 1 Testing Rules (especially the E2E Tests section).
  2. Read plancasting/_codegen-context.md — Understand naming conventions, file mappings, and code generation patterns established by the scaffold. If missing, WARN: "Scaffold context not found. Proceed with manual directory scanning."
  3. Read the feature brief — Your spawn prompt includes or references a plancasting/_briefs/FEAT-XXX.md file.
  4. Read PRD sections — Check plancasting/prd/04-epics-and-user-stories.md for acceptance criteria (Given-When-Then), plancasting/prd/06-user-flows.md for E2E flow paths, plancasting/prd/14-testing-strategy.md for test strategy.
  5. Read BRD security requirements — Check plancasting/brd/13-security-requirements.md for auth and validation rules that E2E tests must verify.
  6. Read the implementation — Examine the backend and frontend code that was just written.
  7. Check plancasting/tech-stack.md — Use the specified test runner and testing libraries. Check the Session Language setting — write user-facing strings (UI labels, toast messages, error messages) in that language. Code and comments remain in English.

Scaffold Inventory

Before writing ANY test code, check for existing scaffold test files:

  1. Run ls e2e/ to identify existing files for this feature.
  2. Check plancasting/_scaffold-manifest.md for E2E test scaffold mappings.
  3. If scaffold E2E files exist (from Stage 3 Teammate 5), implement inside them rather than creating new files. never create duplicate files alongside scaffold files.

Read the full file on GitHub · 129 lines

Changes

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.

  1. 16d ago Changed · +1 lines cc121cacd95b
  2. 1mo ago First seen · 128 lines · 244 tokens per session scan A 4a7fcde76dcf

Subscribe to this mod's changes

feature-tests is an agent published in the GitHub repository VoxTechnologies/transmute-framework (5 stars, last pushed 5d ago), licensed MIT. It adds 244 tokens to every session and 1,849 once invoked, about $0.0010 per session on Opus 5.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-08-31.

Claude CodeCode GenerationE2E testingTestingai-agentautomationclaude-code-pluginplan-casting
Related

Other agents, from other repositories

frontend-evaluator

Frontend QA evaluator. Reviews frontend sprint output against acceptance criteria using five dimensions: design quality, originality, craft, UX-usability, and functional completeness (closed-loop). Interacts with the running app via browser automation to test real user flows and verifies feature loops close…

superduke/ganvil · 68 tokens

tester

Writes component, integration, and E2E tests. All non-unit tests run via Testkube in Kubernetes.

LiorCohen/sdd · 25 tokens

integration-test-reviewer

Reviews changed integration and E2E tests against skeletons, proof obligations, or explicit prompt claims. Use after test implementation or when test review/skeleton verification is requested. Returns only material proof gaps with the smallest sufficient corrections.

shinpr/claude-code-workflows · 50 tokens

output-ux-reviewer

Review a cli-web- CLI from the end-user perspective by RUNNING it. Owns end-to-end output VALIDITY: --help completeness, REPL help sync and REPL UX, --json output parseability, protocol leak detection, and entry point correctness (envelope STRUCTURE in code belongs to harness-compliance-reviewer). Returns scored…

ItamarZand88/CLI-Anything-WEB · 85 tokens

ux-evaluator

Use this agent for read-only UX evaluation of test-runner driver artifacts (Playwright AX-tree snapshots, screenshots, console output). Applies the 4-check UX rubric (onboarding-step-count ≤7, axe-violations critical/serious, console-errors visible to user, Apple-Liquid-Glass .glassEffect() conformance on SwiftUI 26+)…

Kanevry/session-orchestrator · 199 tokens

test-generator

Scan codebase for test gaps and generate unit/integration/E2E tests that actually pass — no hollow tests, no false coverage.

pillip/claude-dev-kit · 30 tokens