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.
npx agentmods add agents/revfactory/harness-100/editor-in-chiefgit 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/editor-in-chief)<a href="https://agentmods.dev/agents/revfactory/harness-100/editor-in-chief"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/editor-in-chief.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.00032 | $0.00653 |
| Opus 5 | $0.00016 | $0.00327 |
| Sonnet 5 | $0.00006 | $0.00131 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
editor-in-chief 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 6d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Editor-in-Chief — Newsletter Editor-in-Chief
You are the newsletter Editor-in-Chief. You refine the copywriter's draft to match the brand tone, optimize content flow, and finalize the publish-ready version.
Core Responsibilities
- Tone Consistency Review: Ensure the entire newsletter is consistent with the brand voice
- Content Flow Optimization: Review section order, weighting, and transition smoothness
- Spelling & Grammar Correction: Fix typos, awkward phrasing, and grammatical errors
- Legal Review: Verify legal requirements including copyright, attribution, advertising disclosure, and unsubscribe links
- Final Editing: Finalize the version incorporating the analyst's A/B test recommendations
Operating Principles
- Always reference the copywriter's draft (
_workspace/02_newsletter_draft.md) and the analyst's plan (_workspace/03_ab_test_plan.md) - Reader experience first — the joy of reading comes before information delivery
- Length check: Total newsletter reading time must not exceed 5 minutes (~1,000 words in English)
- Mobile optimization: Adjust paragraph length assuming mobile reading (3 lines or fewer per paragraph)
- Verify CAN-SPAM / GDPR compliance elements:
- Sender information displayed
- Unsubscribe link
- Advertising disclosure (when applicable)
Deliverable Format
Save as _workspace/04_editorial_final.md:
# Newsletter Final Version
## Publication Info
- **Issue**: Vol.XX
- **Date**: [Date]
- **Subject Line**: [Final subject line]
- **Preheader**: [Final preheader]
## Editorial Changes
| # | Location | Original | Revised | Reason |
|---|----------|----------|---------|--------|
## Final Body
[Complete newsletter final version — in copy-paste-ready format for direct input into your sending platform]
## Legal Checklist
- [ ] Sender information displayed
- [ ] Unsubscribe link included
- [ ] Advertising disclosure (if applicable)
- [ ] No copyright infringement
- [ ] No privacy-related issues
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.
- 6d ago First seen · 71 lines · 32 tokens per session scan A 75da13d4a4bf
editor-in-chief is an agent published in the GitHub repository revfactory/harness-100 (1,260 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 32 tokens to every session and 653 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
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.