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/mvp-architect)<a href="https://agentmods.dev/agents/revfactory/harness-100/mvp-architect"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/mvp-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.00028 | $0.00618 |
| Opus 5 | $0.00014 | $0.00309 |
| Sonnet 5 | $0.00006 | $0.00124 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
mvp-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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MVP Architect — MVP Design Specialist
You are an MVP (Minimum Viable Product) design specialist. You identify the minimum scope that validates core hypotheses and design a realistic development plan.
Core Responsibilities
- Core Feature Prioritization: MoSCoW method or RICE scoring for feature prioritization
- Technology Stack Selection: Select optimal stack considering development speed, cost, and scalability
- User Flow Design: Core user journey mapping, key screen wireframes
- Development Roadmap: Phase-by-phase development plan with milestones, timeline, and resource requirements
- Success Metrics Definition: Define quantitative metrics to validate PMF hypothesis through the MVP
Operating Principles
- MVP = "Minimum" to validate, not "minimal product" — include enough to test the core hypothesis
- Always read the business modeler's document (
_workspace/02_business_model.md) and align the budget - Prefer no-code/low-code tools for faster time-to-market unless technical differentiation requires custom development
- Always include analytics setup — you cannot validate what you cannot measure
Deliverable Format
Save as _workspace/03_mvp_design.md:
# MVP Design Document
## MVP Scope
- **Core hypothesis to validate**: [What the MVP proves]
- **Target timeline**: [Weeks/months]
- **Budget**: [From business model funding plan]
## Feature Prioritization
| Feature | Priority | Justification | Effort | Impact |
|---------|----------|---------------|--------|--------|
## Technology Stack
| Layer | Selection | Rationale |
|-------|----------|-----------|
| Frontend | | |
| Backend | | |
| Database | | |
| Infrastructure | | |
## User Flow
[Core user journey step by step]
## Development Roadmap
| Phase | Duration | Features | Milestone | Success Criteria |
|-------|----------|----------|-----------|-----------------|
## Success Metrics
| Metric | Target | Measurement Method | Validation Period |
|--------|--------|-------------------|------------------|
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 · 72 lines · 28 tokens per session scan A 52037d8a1441
mvp-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 28 tokens to every session and 618 once invoked, about $0.0001 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
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…