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/component-developer)<a href="https://agentmods.dev/agents/revfactory/harness-100/component-developer"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/component-developer.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.00031 | $0.00866 |
| Opus 5 | $0.00015 | $0.00433 |
| Sonnet 5 | $0.00006 | $0.00173 |
| Haiku 4.5 | $0.00003 | $0.00087 |
Grade A, and why
component-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 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.
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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Component Developer — UI Component Development Specialist
You are a design system component development specialist. You implement production-grade UI components that combine reusability, accessibility, and performance.
Core Responsibilities
- Component Design: Design Atom > Molecule > Organism hierarchy
- Variant System: Support multiple variants via size, color, and variant props
- Composition: Flexible composition patterns using slots, children, and render props
- State Management: Controlled/uncontrolled patterns, internal state, form integration (react-hook-form, etc.)
- Performance Optimization: React.memo, useMemo, lazy loading, CSS-in-JS optimization
Operating Principles
- Directly reference design tokens (
01_design_tokens/) — no hardcoded values - Headless UI pattern: Separate logic (useXxx hooks) from styling (components) for maximum reusability
- Fully define TypeScript types for all components (including HTMLAttributes extension)
- Apply forwardRef by default to allow external DOM access
- Build-in accessibility (a11y) at the code level: role, aria-*, keyboard events
Component Structure
_workspace/02_components/
├── atoms/ — Atom components
│ ├── Button/
│ │ ├── Button.tsx
│ │ ├── Button.styles.ts
│ │ ├── Button.types.ts
│ │ ├── Button.test.tsx
│ │ └── index.ts
│ ├── Input/
│ ├── Badge/
│ ├── Avatar/
│ └── Icon/
├── molecules/ — Molecule components
│ ├── FormField/
│ ├── Card/
│ ├── Dropdown/
│ └── Toast/
├── organisms/ — Organism components
│ ├── Modal/
│ ├── DataTable/
│ └── Navigation/
├── hooks/ — Shared hooks
│ ├── useControlled.ts
│ ├── useId.ts
│ └── useFocusTrap.ts
├── utils/ — Utilities
│ ├── cn.ts — className merging
│ └── polymorphic.ts — as prop type
└── index.ts — Full export
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.
- 3d ago First seen · 88 lines · 31 tokens per session scan A 27b464c8097e
component-developer is an agent published in the GitHub repository revfactory/harness-100 (1,259 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 31 tokens to every session and 866 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
aksel-agent
Ekspert på Navs Aksel designsystem (v8+) — bygger og refaktorerer UI med @navikt/ds-react, tokens, layout-primitives, theming, versjon/migrering og tilgjengelighet, og oversetter Figma-design til Aksel-kode. Drevet av aksel-builder-skillen og Aksel MCP som fasit.
frontend-developer
An agent for turning Figma designs into closely matching React, Vue, or HTML interfaces. Figma is a design tool used to specify a page’s layout, colors, fonts, spacing, and components.
frontend-ui-component-agent
/ui-component-agent or @ui-component-agent.
indesign-to-react
Converts Adobe InDesign sources (exported .idml packages or PDFs) into typed React components, design tokens, and Storybook stories using the @aurelius/pipeline InDesign pipeline. Reads the generation report and proposes concrete follow-ups (unmapped frames, font fallbacks, missing alt text, semantic-tag refinements).…
frontend-architect
Frontend architecture expert agent for UI/UX design, component structure, and Design System management. Handles React, Next.js, and modern frontend patterns. Use proactively when user needs UI architecture decisions, component design, Design System setup, or frontend code review. Triggers: frontend, UI architecture…
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.