tc-frontend-tester

tc-frontend-tester is an agent for Claude Code from codeoutin/claude-code-agency. It costs 22 tokens per session (3,499 once invoked), scanned A, original, MIT.

A frontend-testing agent that uses Playwright to check websites and web applications. Playwright is a browser-testing tool that can automate clicks, typing, and page checks across user flows.

In plain words
What is it for?
Use it to test pages, forms, user journeys, responsiveness, visual behavior, and other aspects of the user experience.
Why use it?
It helps find broken interactions, layout problems, and responsive behavior issues before release. It follows the approved implementation and test context and records missing access credentials when needed.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: names the TodoWrite tool.

Good fit Use it to test pages, forms, user journeys, responsiveness, visual behavior, and other aspects of the user experience.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/codeoutin/claude-code-agency/tc-frontend-tester
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/codeoutin/claude-code-agency

Made for: Claude Code.

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 tc-frontend-tester

README.md
[![agentmods](https://agentmods.dev/badge/agents/codeoutin/claude-code-agency/tc-frontend-tester/github.svg)](https://agentmods.dev/agents/codeoutin/claude-code-agency/tc-frontend-tester)
Your own site
<a href="https://agentmods.dev/agents/codeoutin/claude-code-agency/tc-frontend-tester"><img src="https://agentmods.dev/badge/agents/codeoutin/claude-code-agency/tc-frontend-tester/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 tc-frontend-tester

Your own site · 80×15
<a href="https://agentmods.dev/agents/codeoutin/claude-code-agency/tc-frontend-tester"><img src="https://agentmods.dev/badge/agents/codeoutin/claude-code-agency/tc-frontend-tester.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,499 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00022 $0.03499
Opus 5.5 $0.00009 $0.01400
Sonnet 5.5 $0.00004 $0.00700
Haiku 4.5 $0.00002 $0.00350

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

Security

Grade A, and why

tc-frontend-tester scanned grade A with 1 finding 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 2mo 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

if curl -s http://localhost:3000 > /dev/null 2>&1; then
agents/tc-frontend-tester.md · 415 lines

How it starts

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

You are the Frontend Tester ensuring perfect user experience for the task-complete workflow.

TASK DIRECTORY: {task_directory_path}

Mission

Validate implemented features deliver flawless user experiences matching enterprise standards with professional design, perfect responsiveness, and intuitive interactions users will pay for.

Inputs Required

1. Implementation Context

Read {task_directory_path}/plan.md for test scenarios and quality expectations. Read {task_directory_path}/review-{final_cycle}.md for approved functionality details.

2. Testing Credentials

Primary Test Account:

  • Email: [Configure for your project]
  • Password: [Configure for your project]

Fallback: If credentials fail, document requirement for user to provide working test credentials.

Comprehensive Testing Protocol

1. Pre-Testing Setup

Dev Server Status Verification

Before testing, verify development environment is stable:

# Check if dev monitor reported stable status
if [ -f "{task_directory_path}/dev-status.json" ]; then
  DEV_STATUS=$(jq -r '.status' {task_directory_path}/dev-status.json)
  if [ "$DEV_STATUS" != "stable" ]; then
    echo "❌ Cannot proceed with testing - dev monitor reports: $DEV_STATUS"
    echo "Active errors detected:"
    jq '.errors[]' {task_directory_path}/dev-status.json
    echo "Frontend testing requires stable development environment"
    exit 1
  fi
  echo "✅ Dev monitor reports stable status - proceeding with tests"
else
  echo "⚠️  No dev monitor status file found - starting dev server"
  # Start development server ourselves and wait for it to be ready
  npm run dev > {task_directory_path}/frontend-tester-dev.log 2>&1 &
  DEV_PID=$!
  echo $DEV_PID > {task_directory_path}/frontend-tester-dev.pid
  
  echo "Waiting for dev server to start..."
  sleep 10
  
  # Test if server is responsive
  for i in {1..30}; do
    if curl -s http://localhost:3000 > /dev/null 2>&1; then
      echo "✅ Dev server started and responsive"
      break
    fi
    sleep 2
  done
  
  if ! curl -s http://localhost:3000 > /dev/null 2>&1; then
    echo "❌ Dev server failed to start or is not responsive"
    kill $DEV_PID 2>/dev/null
    exit 1
  fi
fi

Read the full file on GitHub · 415 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. 2mo ago First seen · 415 lines · 22 tokens per session scan A d7e7cdfff82b

Subscribe to this mod's changes

tc-frontend-tester is an agent published in the GitHub repository codeoutin/claude-code-agency (42 stars, last pushed 8mo ago), licensed MIT. It adds 22 tokens to every session and 3,499 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

tc-frontend-tester compared with agents from other repositories

tc-frontend-tester next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
tc-frontend-testercodeoutin/claude-code-agencyAgent428mo agoMITA22Claude Code
integration-testing-orchestratoreunomia-bpf/agentsightAgent7756d agoMITA0Claude Code
qa-testerdatit309/supergraphAgent237d agoMITA41Claude Code
qa-engineerodarino/harenAgent113d agoMITA21Claude Code
qa-testercskwork/oh-my-symphonyAgent399d agoApache-2.0A49Claude Code
playwright-test-generatorRaNDoM6913/claude-code-superkitAgent32d agoMITA17Claude Code
e2e-testermnzralee/claude-multi-agent-architectureAgent81mo agoMITA41Claude Code