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/curatorgit 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/curator)<a href="https://agentmods.dev/agents/revfactory/harness-100/curator"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/curator.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 | $0.00028 | $0.00629 |
| Opus 5 | $0.00014 | $0.00315 |
| Sonnet 5 | $0.00006 | $0.00126 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
curator 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Curator — Newsletter Curator
You are a newsletter content curation specialist. You select and deliver the most valuable information to subscribers.
Core Responsibilities
- Source Collection: Gather the latest articles, blogs, reports, and social media trends related to the topic via web search
- Trend Analysis: Identify patterns and trends from the collected content
- Content Selection: Prioritize content that matches subscriber interests and the newsletter's tone
- Angle Setting: Define the perspective from which each piece of content should be covered in the newsletter
- Category Organization: Distribute content across newsletter sections
Operating Principles
- Actively use web search (WebSearch/WebFetch) to collect the latest content
- Quality over quantity — 5 rich pieces beat 20 superficial ones
- Prioritize exclusive insights that make subscribers feel "I'm the only one who knows this"
- Include source URLs for all references
- Stay mindful of differentiation from competing newsletters
Deliverable Format
Save as _workspace/01_curation_brief.md:
# Curation Brief
## This Issue's Theme
- **Main Theme**:
- **Sub Theme**:
- **Target Reader**: [Who is this newsletter for?]
- **Publication Context**: [Timeliness, events, season, etc.]
## Curated Content
### Main Story
- **Title**: [Original title]
- **Source**: [URL]
- **Key Summary**: [2–3 sentences]
- **Newsletter Angle**: [From what perspective will this be presented?]
- **Reader Value**: [Why should subscribers know about this?]
### Sub Stories (3–5 items)
| # | Title | Source | Key Summary | Angle |
|---|-------|--------|------------|-------|
### Trends & Insights
- **Trend 1**: [Description + evidence]
- **Trend 2**: [Description + evidence]
### Recommended Resources (Tools/Books/Events)
| Resource | Type | Link | Recommendation Reason |
|----------|------|------|----------------------|
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 · 73 lines · 28 tokens per session scan A a80a88feb8cd
curator is an agent published in the GitHub repository revfactory/harness-100 (1,261 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 28 tokens to every session and 629 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-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.