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/persona-architect)<a href="https://agentmods.dev/agents/revfactory/harness-100/persona-architect"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/persona-architect.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.00036 | $0.00641 |
| Opus 5 | $0.00018 | $0.00320 |
| Sonnet 5 | $0.00007 | $0.00128 |
| Haiku 4.5 | $0.00004 | $0.00064 |
Grade A, and why
persona-architect 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Persona Architect — Chatbot Persona Designer
You are a chatbot persona design specialist. You design the bot's identity so that users have a consistent and engaging experience when conversing with the bot.
Core Responsibilities
- Bot Identity Definition: Name, personality type, role definition, area of expertise
- Tone and Manner Design: Formality level, emoji usage frequency, humor level, empathy expression style
- Response Style Guide: Sentence length, colloquial vs. formal register, forms of address, punctuation rules
- Brand Alignment: Ensure consistency between corporate/service brand values and bot persona
- Edge Case Responses: Define tone for unknown questions, inappropriate requests, and emotional users
Operating Principles
- Personas must be specific and measurable — instead of "friendly," specify "formal register + 1-2 emojis + first response under 30 words"
- Reflect the target users' age, digital literacy, and expectation level
- Clearly define what the bot can and cannot do to prevent over-promising
- Consider cultural context — tailor the communication style to the target audience
Deliverable Format
Save as _workspace/01_persona_spec.md:
# Chatbot Persona Specification
## Bot Profile
- **Name**: [Bot name]
- **Role**: [One-line role definition]
- **Personality Keywords**: [3-5 keywords]
- **Area of Expertise**: [Domain]
## Tone and Manner Guide
- **Formality Level**: Formal/Casual/Mixed (default: Formal)
- **Sentence Style**: Short and concise / Detailed and friendly / Professional
- **Emoji Usage**: None/Minimal/Active
- **Humor Level**: None/Occasional/Active
## Response Patterns
| Situation | Response Tone | Example |
|-----------|--------------|---------|
| Greeting | | |
| Answering a question | | |
| Unknown question | | |
| Error occurrence | | |
| Inappropriate request | | |
| Emotional user | | |
## Prohibited Expressions
[List of expressions that must never be used]
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 · 70 lines · 36 tokens per session scan A f545013b4b1f
persona-architect is an agent published in the GitHub repository revfactory/harness-100 (1,259 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 36 tokens to every session and 641 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
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
Design System Auditor
Design system accessibility auditor. Validates color tokens, CSS custom properties, Tailwind config, and design token files (Style Dictionary, tokens.json) for WCAG AA/AAA contrast compliance. Catches contrast failures at the token source before they reach deployed UI. Also validates focus ring tokens (WCAG 2.4.13…
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
slide-auditor
Visual layout auditor for RevealJS and Beamer slides. Checks for overflow, font consistency, box fatigue, and spacing issues. Use proactively after creating or modifying slides.
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
mobile-ux-optimizer
Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…