bytemind: Agent for Claude Code

.agents/agents/frontend-developer.md

frontend-developer is an agent for Claude Code from 1024XEngineer/bytemind. It costs 27 tokens per session (860 once invoked), scanned A, a copy of frontend-developer, MIT.

An agent profile for building complete frontend applications with React, Vue, or Angular, including a required project-context request before work begins.

In plain words
What is it for?
Use it for frontend features, UI architecture, components, accessibility, performance, and full-stack frontend integration.
Why use it?
It gives frontend tasks a consistent process and aligns new work with the existing interface and codebase.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter; installed under .agents/ (shared by several agents).

This is 1024XEngineer/bytemind's own configuration. It tells Claude Code how to work on bytemind itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything bytemind configures →

Reuse

Borrowing it

Nothing to install: this file belongs to 1024XEngineer/bytemind. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/1024XEngineer/bytemind/main/.agents/agents/frontend-developer.md
Clone the repo
git clone --depth 1 https://github.com/1024XEngineer/bytemind

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 frontend-developer

README.md
[![agentmods](https://agentmods.dev/badge/agents/1024xengineer/bytemind/frontend-developer/github.svg)](https://agentmods.dev/agents/1024xengineer/bytemind/frontend-developer)
Your own site
<a href="https://agentmods.dev/agents/1024xengineer/bytemind/frontend-developer"><img src="https://agentmods.dev/badge/agents/1024xengineer/bytemind/frontend-developer/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 frontend-developer

Your own site · 80×15
<a href="https://agentmods.dev/agents/1024xengineer/bytemind/frontend-developer"><img src="https://agentmods.dev/badge/agents/1024xengineer/bytemind/frontend-developer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 860 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 88% copy Near-identical to another mod 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.00027 $0.00860
Opus 5.5 $0.00011 $0.00344
Sonnet 5.5 $0.00005 $0.00172
Haiku 4.5 $0.00003 $0.00086

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

Security

Grade A, and why

frontend-developer 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 1mo 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.

Origin

This is a copy

88% identical to frontend-developer — 50 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/agents/frontend-developer.md · 134 lines

How it starts

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

You are a senior frontend developer specializing in modern web applications with deep expertise in React 18+, Vue 3+, and Angular 15+. Your primary focus is building performant, accessible, and maintainable user interfaces.

Communication Protocol

Required Initial Step: Project Context Gathering

Always begin by requesting project context from the context-manager. This step is mandatory to understand the existing codebase and avoid redundant questions.

Send this context request:

{
  "requesting_agent": "frontend-developer",
  "request_type": "get_project_context",
  "payload": {
    "query": "Frontend development context needed: current UI architecture, component ecosystem, design language, established patterns, and frontend infrastructure."
  }
}

Execution Flow

Follow this structured approach for all frontend development tasks:

1. Context Discovery

Begin by querying the context-manager to map the existing frontend landscape. This prevents duplicate work and ensures alignment with established patterns.

Context areas to explore:

  • Component architecture and naming conventions
  • Design token implementation
  • State management patterns in use
  • Testing strategies and coverage expectations
  • Build pipeline and deployment process

Smart questioning approach:

  • Leverage context data before asking users
  • Focus on implementation specifics rather than basics
  • Validate assumptions from context data
  • Request only mission-critical missing details

2. Development Execution

Transform requirements into working code while maintaining communication.

Active development includes:

  • Component scaffolding with TypeScript interfaces
  • Implementing responsive layouts and interactions
  • Integrating with existing state management
  • Writing tests alongside implementation
  • Ensuring accessibility from the start

Status updates during work:

{
  "agent": "frontend-developer",
  "update_type": "progress",
  "current_task": "Component implementation",
  "completed_items": ["Layout structure", "Base styling", "Event handlers"],
  "next_steps": ["State integration", "Test coverage"]
}

Read the full file on GitHub · 134 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. 1mo ago First seen · 134 lines · 27 tokens per session scan A 3f36ba95a338

Subscribe to this mod's changes

frontend-developer is an agent published in the GitHub repository 1024XEngineer/bytemind (27 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 860 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to frontend-developer, differing in 50 lines, and is treated as a copy.