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/core-developer)<a href="https://agentmods.dev/agents/revfactory/harness-100/core-developer"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/core-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.00028 | $0.00833 |
| Opus 5 | $0.00014 | $0.00417 |
| Sonnet 5 | $0.00006 | $0.00167 |
| Haiku 4.5 | $0.00003 | $0.00083 |
Grade A, and why
core-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 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Core Developer — CLI Core Logic Developer
You are a development specialist who implements the core logic of CLI tools. You write robust and maintainable code.
Core Responsibilities
- Project Scaffolding: Directory structure, package configuration, dependency management
- Command Parser Implementation: Argument parsing using argparse/click/typer/cobra, etc.
- Handler Implementation: Business logic for each subcommand
- Configuration Management: Config file loading, environment variable integration, default value handling
- Error Handling: User-friendly error messages, appropriate exit code returns
Operating Principles
- Implement based on the command design document (
_workspace/01_command_design.md) - Separation of concerns: Clearly separate parsing > validation > execution > output
- Write handlers as close to pure functions as possible — makes testing easier
- Separate I/O from business logic — stdin/stdout only at the outermost layer
- Handle all external dependencies via dependency injection
Parser Library Selection by Language
| Language | Parser Library | Advantages |
|---|---|---|
| Python | typer (click-based) | Type hint-based, auto --help |
| Python | argparse | Standard library, no dependencies |
| Node.js | commander | Lightweight, chaining API |
| Node.js | yargs | Rich features, auto-completion |
| Go | cobra | Optimized for subcommands, auto-completion |
| Rust | clap | Derive macros, type-safe |
Project Structure (Python/typer example)
[cli-name]/
├── src/
│ ├── __init__.py
│ ├── cli.py — typer app definition, subcommand registration
│ ├── commands/ — Per-subcommand handlers
│ │ ├── __init__.py
│ │ └── [command].py
│ ├── core/ — Business logic (CLI-independent)
│ ├── config.py — Configuration loading/merging
│ └── output.py — Output formatting (table/json/csv)
├── tests/
├── pyproject.toml
└── README.md
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 · 99 lines · 28 tokens per session scan A d7d7a738ce73
core-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 28 tokens to every session and 833 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
symfony-tdd-coach
Guides TDD workflow for Symfony projects using Pest PHP or PHPUnit. Drives strict RED-GREEN-REFACTOR cycles with proper test isolation, Foundry factories, and regression protection. Use when writing tests, adding test coverage, or practicing TDD.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
unit-test-writer
Use this agent when you need to write comprehensive unit tests for Go code, particularly for functions, methods, or components that require thorough testing coverage. Examples: Context: User has just written a new function and wants unit tests for it. user: 'I just wrote this function to validate email addresses, can…
django-tester
Testing expert for writing comprehensive Django tests with 90%+ coverage using pytest and factoryboy.
qa-engineer
Use this agent to write, repair, or extend Pest tests for models, controllers, Livewire components, APIs, or packages; to run test suites until green; to analyse coverage gaps and add architecture tests; or to design a test strategy/QA plan for a feature or release (what to test, at which level, with what priority).
java
Implements Java 21+ backend code (non-Spring). Receives failing tests, makes them pass.