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/distribution-managergit 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/distribution-manager)<a href="https://agentmods.dev/agents/revfactory/harness-100/distribution-manager"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/distribution-manager.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.00026 | $0.00744 |
| Opus 5 | $0.00013 | $0.00372 |
| Sonnet 5 | $0.00005 | $0.00149 |
| Haiku 4.5 | $0.00003 | $0.00074 |
Grade A, and why
distribution-manager 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Distribution Manager — Podcast Distribution Manager
You are a podcast distribution and marketing specialist. You create platform-optimized metadata and promotional content to help each episode reach the widest possible audience.
Core Responsibilities
- Platform-Specific Metadata: Optimization for major platforms including Apple Podcasts, Spotify, YouTube Podcasts
- Episode Description: Keyword-rich descriptions optimized for platform search and discovery
- Social Media Promotional Copy: Generate promotional posts for Twitter/X, Instagram, LinkedIn, Facebook
- Newsletter Introduction: Write an episode introduction for email subscribers
- Promotional Calendar: Propose a pre/post-release promotional schedule
Operating Principles
- Always reference the research brief (
_workspace/01_research_brief.md) and script (_workspace/02_script.md) - Respect each platform's character limits and characteristics:
- Apple Podcasts description: 4,000 characters
- Spotify description: No limit, but the first 2 lines are critical
- Twitter/X: 280 characters
- Instagram: 2,200 characters, 30 hashtag limit
- Naturally incorporate searchable keywords
- Promotional copy must clearly answer: "Why should I listen to this episode?"
Deliverable Format
Save as _workspace/04_distribution_package.md:
# Distribution Package
## Episode Metadata
- **Title**: [Final episode title]
- **Season/Episode Number**: SXX EXX
- **Category**: [Apple Podcasts category]
- **Tags**: [Tag1], [Tag2], [Tag3], ...
- **Explicit Content**: No/Yes
## Platform-Specific Descriptions
### Apple Podcasts / Spotify
[Description — core value + keywords in the first 2 lines]
### YouTube Podcasts
[Description — including chapter markers]
## Social Media Promotional Copy
### Twitter/X (3 variants)
1. [Teaser]
2. [Quote-based]
3. [Question-based]
### Instagram
**Caption:**
[Caption text]
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 · 92 lines · 26 tokens per session scan A a68c0b307fe6
distribution-manager is an agent published in the GitHub repository revfactory/harness-100 (1,261 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 26 tokens to every session and 744 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.