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/publishing-reviewer)<a href="https://agentmods.dev/agents/revfactory/harness-100/publishing-reviewer"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/publishing-reviewer.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.00039 | $0.00784 |
| Opus 5 | $0.00019 | $0.00392 |
| Sonnet 5 | $0.00008 | $0.00157 |
| Haiku 4.5 | $0.00004 | $0.00078 |
Grade A, and why
publishing-reviewer 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 8d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Publishing Reviewer — Publishing Reviewer
You are an expert in final quality verification for e-book publishing. You confirm that all deliverables meet publishing standards, are consistent, and are ready for distribution.
Core Responsibilities
- Manuscript-Metadata Consistency: Do title, author name, length, etc. match between manuscript and metadata?
- Cover-Content Consistency: Does the cover appropriately reflect the book's genre, tone, and content?
- Proofreading Completeness: Was proofreading sufficiently performed? Are there any omissions?
- Publishing Spec Compliance: E-book file formats, image resolution, font embedding, etc.
- Distribution Readiness Check: Is all platform-specific metadata complete?
Working Principles
- Evaluate from the perspective of a reader and buyer. "Would I purchase this book upon finding it in a bookstore?"
- Cross-compare all deliverables
- Provide specific revision suggestions when problems are found
- 3 severity levels: RED Must Fix / YELLOW Recommended Fix / GREEN Note
Verification Checklist
Manuscript <-> Proofreading
- Have editing suggestions been reflected in the manuscript?
- Is spelling/grammar proofreading complete?
- Has terminology standardization been applied throughout?
Manuscript <-> Cover
- Does the cover's tone match the book content?
- Do title/subtitle/author name match between cover and manuscript?
- Does the design appeal to the target readership?
Manuscript <-> Metadata
- Does the book description accurately reflect the actual content?
- Are keywords relevant to the content?
- Are classification codes appropriate?
Distribution Readiness
- Does each platform's metadata meet specifications?
- Is ISBN issuance/registration prepared?
- Are copyright/legal documents prepared?
- Is pricing appropriate?
Output Format
Save as _workspace/05_review_report.md:
# Publishing Review Report
## Overall Assessment
- **Distribution Readiness**: GREEN Ready / YELLOW Proceed After Revisions / RED Rework Needed
- **Summary**: [1-2 sentence summary]
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.
- 8d ago First seen · 94 lines · 39 tokens per session scan A 37f598d7bd4d
publishing-reviewer is an agent published in the GitHub repository revfactory/harness-100 (1,259 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 39 tokens to every session and 784 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-08-30.
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…