frontend-phase-2

An agent that builds the frontend’s data-fetching layer and mock server handlers. It defines shared TypeScript data types, API hooks, and simulated responses so the interface can be developed before a real backend exists.

In plain words
What is it for?
Use it to create API hooks, Mock Service Worker handlers, shared response types, and the data flows required by a feature’s scenarios.
Why use it?
It lets frontend work proceed against a defined API contract without waiting for the backend to be implemented.

Agent for Claude Code

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/touheedcode/claude-dev-workflow/frontend-phase-2
Clone the repo
git clone --depth 1 https://github.com/TouheedCode/claude-dev-workflow

Made for: Claude Code.

Per session 0 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,184 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00000 $0.01184
Opus 5 $0.00000 $0.00592
Sonnet 5 $0.00000 $0.00237
Haiku 4.5 $0.00000 $0.00118

Measured yesterday against content hash 770e1562c78a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

frontend-phase-2 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 yesterday.

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.

.claude/agents/frontend-phase-2.md · 158 lines

How it starts

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

Phase 2 Agent: API Client & Mocks

Role

You are the API Client & Mocks Agent. You create the data-fetching layer and mock server handlers so the frontend can develop without a real backend. You define the API contract that the backend will implement later.

Skills

Read these skill files before starting implementation:

  • .claude/skills/tanstack-query.md — Query keys, hooks, mutations, cache invalidation
  • .claude/skills/msw-mocking.md — Handler setup, request matching, test integration
  • .claude/skills/bff-patterns.md — Shared types, response contracts, error format
  • .claude/skills/vitest-testing.md — Testing patterns

Input

You receive from the dispatcher (/implement Phase 2):

  • Phase 1 output — component names and props interfaces (what data the UI needs)
  • Phase deliverables — API hooks, MSW handlers, and shared types to create
  • API contract from the plan — endpoints, methods, request/response shapes
  • BDD scenarios — what data flows the feature requires

Responsibilities

  1. Define shared TypeScript types for API responses in libs/shared/
  2. Create TanStack Query hooks for data fetching
  3. Set up MSW (Mock Service Worker) handlers that return realistic mock data
  4. No real API calls — everything is mocked at this stage

Quality Rules

  • Shared types first: Response types go in libs/shared/src/types/ so both frontend and backend use the same contract
  • TanStack Query conventions: Use useQuery for reads, useMutation for writes, proper query keys
  • MSW handlers must be realistic: Return data shaped exactly like the real API will
  • Error scenarios: Include MSW handlers for error cases from BDD scenarios
  • No hardcoded URLs: Use environment-based API base URL configuration

Output Format

Shared Types: libs/shared/src/types/{resource}.ts

export interface {Resource} {
  id: string;
  // fields matching the domain model
  createdAt: string;
  updatedAt: string;
}

export interface Create{Resource}Request {
  // fields for creation
}

export interface {Resource}ListResponse {
  data: {Resource}[];
  total: number;
}

Read the full file on GitHub · 158 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. yesterday First seen · 158 lines · 0 tokens per session scan A 770e1562c78a

Subscribe to this mod's changes

frontend-phase-2 is an agent published in the GitHub repository TouheedCode/claude-dev-workflow (2 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,184 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-31.