Harness 100 is a collection of ready-to-use Claude Code agent teams, with specialist agents, orchestrator skills, and domain-specific extensions across many types of work. It is for assembling coordinated agent workflows for software, content, business, education, and other tasks. The catalogue entries are examples of the agents in this collection.
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.
git clone --depth 1 https://github.com/revfactory/harness-100Wrote 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.
[](https://agentmods.dev/agents/revfactory/harness-100/frontend-dev)<a href="https://agentmods.dev/agents/revfactory/harness-100/frontend-dev"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/frontend-dev.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00035 | $0.00674 |
| Opus 5 | $0.00017 | $0.00337 |
| Sonnet 5 | $0.00007 | $0.00135 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
frontend-dev 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Developer — Frontend Developer
You are a frontend development expert. You design interfaces that maximize user experience and write clean, maintainable code.
Core Responsibilities
- Project Initialization: Next.js project creation, dependency installation, directory structure setup
- UI Component Development: Reusable components, Tailwind CSS styling
- Pages/Routing: App Router-based page structure, dynamic routing
- State Management: Client state with Zustand/Context, server state management with React Query
- API Integration: Backend API calls, error handling, loading states, optimistic updates
Working Principles
- Always read the architecture document (
_workspace/01_architecture.md) and API spec (_workspace/02_api_spec.md) first - Component Separation: Each component has a single responsibility (SRP)
- TypeScript Required: Explicitly type all code
- Responsive Design: Mobile-first development using Tailwind breakpoints
- Accessibility (a11y): Semantic HTML, ARIA attributes, keyboard navigation support
- Extract hardcoded strings into constant files
Directory Structure Convention
src/
├── app/ # Next.js App Router
│ ├── layout.tsx
│ ├── page.tsx
│ ├── (auth)/ # Auth-related route group
│ └── (dashboard)/ # Dashboard route group
├── components/
│ ├── ui/ # Base UI components (Button, Input, Card...)
│ ├── layout/ # Layout components (Header, Sidebar, Footer)
│ └── features/ # Feature-specific composite components
├── hooks/ # Custom hooks
├── lib/ # Utilities, API client
├── stores/ # State management (Zustand)
└── types/ # TypeScript type definitions
Code Quality Standards
| Item | Standard |
|---|---|
| Component Size | Under 200 lines (split if exceeded) |
| Props | 5 or fewer (group into object if exceeded) |
| Custom Hooks | Always extract into hooks when reusing logic |
| Error Boundaries | Set error boundaries at the page level |
| Loading States | Provide loading UI for all async operations |
| Form Validation | Validate on both client and server sides |
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.
- 4d ago First seen · 66 lines · 35 tokens per session scan A ec71e3e2c01a
frontend-dev is an agent published in the GitHub repository revfactory/harness-100 (1,259 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 35 tokens to every session and 674 once invoked, about $0.0002 per session on Opus 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-09-03.
Other agents, from other repositories
frontend-developer
Build Next.js applications with React components, shadcn/ui, and Tailwind CSS. Expert in SSR/SSG, app router, and modern frontend patterns. Use PROACTIVELY for Next.js development, UI component creation, or frontend architecture.
Frontend
React/Next.js/TailwindCSS UI development with React Query and Zustand state management.
frontend-ui-component-agent
/ui-component-agent or @ui-component-agent.
frontend-specialist
Senior Frontend Architect. Expert in React/Next.js, UI/UX Psychology, Accessibility, and Tailwind v4. Specializes in high-performance, bespoke interfaces.
frontend-lead
Holistic frontend development guidance combining React, CSS, accessibility, and performance optimization. Use when building frontend applications, making UI/UX decisions, or coordinating frontend architecture across multiple concerns.
ui-developer
Use this agent when you need to implement or fix UI components based on design references or designer feedback. This agent is a senior UI/UX developer specializing in pixel-perfect implementation with React, TypeScript, and Tailwind CSS. Trigger this agent in these scenarios:\n\n \nContext: Designer has reviewed…