tc-frontend-tester

tc-frontend-tester is an agent for coding agents 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

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.

agentmods
npx agentmods add agents/codeoutin/claude-code-agency/tc-frontend-tester
Clone the repo
git clone --depth 1 https://github.com/codeoutin/claude-code-agency

Wrote this? Show the measurements

A badge for your README with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them.

agentmods badge for tc-frontend-tester

README.md
[![agentmods](https://agentmods.dev/badge/agents/codeoutin/claude-code-agency/tc-frontend-tester.svg)](https://agentmods.dev/agents/codeoutin/claude-code-agency/tc-frontend-tester)
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. Scan, not verified.
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 $0.00022 $0.03499
Opus 5 $0.00011 $0.01750
Sonnet 5 $0.00004 $0.00700
Haiku 4.5 $0.00002 $0.00350

Measured 3d ago against content hash d7e7cdfff82b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 3d 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. 3d 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 (41 stars, last pushed 6mo ago), licensed MIT. It adds 22 tokens to every session and 3,499 once invoked, about $0.0001 per session on Opus 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

Other agents, from other repositories

e2e-verifier

FlutterアプリのE2E動作検証エージェント。MCP(dart-mcp + Marionette)を使い、シミュレーター上でUI操作・検証を行う。mobile-automationスキルから呼び出される。.

K9i-0/ccpocket · 65 tokens

geo-qa-verifier

Performs independent QA, regression testing, build verification, contract validation, smoke checks, and final PASS/PASS WITH ISSUES/FAIL reports across GEO Optimizer and GeoReady.

Auriti-Labs/geo-optimizer-skill · 42 tokens

test-reporter

Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.

nrslib/takt · 0 tokens

integration-testing-orchestrator

Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…

eunomia-bpf/agentsight · 239 tokens

app-test-debug-agent

アプリのテスト・デバッグ・ログ調査エージェント。Chrome DevTools/Playwright/CloudWatch Logs/ローカル実行/エラー分析を担当。コンテキスト節約のため調査を代行する。.

minorun365/my-claude-code-settings · 60 tokens

playwright-automation-engineer-ts-detailed

Provide expert guidance, code, and troubleshooting help for end-to-end and component-level test automation using Playwright with TypeScript. Full methodology with patterns and examples; use playwright-expert for the concise day-to-day variant.

jaktestowac/awesome-copilot-for-testers · 54 tokens