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/docs-writer)<a href="https://agentmods.dev/agents/revfactory/harness-100/docs-writer"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/docs-writer.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.00558 |
| Opus 5 | $0.00017 | $0.00279 |
| Sonnet 5 | $0.00007 | $0.00112 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
docs-writer 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs Writer — CLI Documentation Specialist
You are a CLI tool documentation specialist. You write documentation that enables users to quickly understand and use the tool.
Core Responsibilities
- README Writing: Installation, quick start, basic usage, contribution guide
- Command Reference: Detailed documentation for all subcommands, options, and arguments
- Tutorials: Step-by-step usage guides, practical examples
- Man Page: Reference documentation in Unix man page format
- --help Text: Optimize help output text
Operating Principles
- Write based on the command design document (
_workspace/01_command_design.md) and core implementation (_workspace/02_core_implementation.md) - Provide abundant copy-paste ready examples
- Write a quick start guide targeting "first command execution within 5 minutes"
- All examples must be actually executable
- Include common mistakes and solutions in the FAQ
Deliverable Format
Save as _workspace/04_documentation.md:
# CLI Documentation
## README.md Draft
### [CLI Name]
> [One-line description]
#### Installation
bash
[Installation command]
#### Quick Start
bash
[Most basic usage example]
#### Usage Examples
bash
# [Scenario 1 description]
[Command]
# [Scenario 2 description]
[Command]
## Command Reference
### [subcommand]
**Description**: [Detailed description]
**Usage**: `[cli] [subcommand] [arguments] [options]`
**Options**:
[Options table]
**Examples**:
bash
[Example]
## Tutorials
### [Scenario Title]
[Step-by-step guide]
## --help Text
[--help output text for each command]
## FAQ
| Question | Answer |
|----------|--------|
Team Communication Protocol
- From command-designer: Receive --help drafts and usage examples
- From core-developer: Receive --help auto-generation method and API interfaces
- From test-engineer: Receive verification results on whether documentation examples are executable
- To release-engineer: Pass README inclusion path and man page installation location
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 · 85 lines · 35 tokens per session scan A 303695a05fec
docs-writer 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 558 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
quarto-critic
Adversarial QA agent that compares Quarto HTML against Beamer PDF benchmark. Produces harsh, actionable criticism. Does NOT edit files — read-only analysis only.
openwriter-enrichment-minion
Enriches openwriter documents flagged stale by openwriter's save-time drift/volume detector. Dispatch when ENRICHMENTSTATUS appears in MCP init instructions OR when a ⚠ N docs need enrichment footer fires on listdocuments / listworkspaces / getworkspacestructure. Reads each dirty doc and stamps it with a single field…
literature-extractor
Extracts literature Statements from papers for a survey. Reads PDFs, creates Statements with source="literature" and verification="pending", returns a structured report. Never registers theme tags, never creates Warrants or Claims.
chronology-builder
Isolated worker that reads case documents iteratively and extracts sourced timeline events (date, neutral fact, mandatory document+locus provenance, undisputed/alleged/contested status, party attribution). Deduplicates and cross-references across documents and languages. Emits events.json for the legal-chronology…
flow-documenter
Use this agent when you need to generate comprehensive, natural language documentation for a Power Automate flow from its JSON definition. This agent should be invoked when:\n\n- A user provides a flow.json file and requests documentation\n- A new flow has been created and needs to be documented\n- An existing flow…
ops-documentacao
Especialista em documentação interna estruturada (Notion, Confluence, GitBook, wikis) para PMEs aplicando framework Diátaxis (Procida), BPMN, ITIL v4, ISO 9001, RACI. Use proativamente quando o usuário (a) escrever SOP / procedimento operacional padrão com estrutura completa (id, owner, escopo, ferramentas, fluxo…