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/shownote-editorgit 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/shownote-editor)<a href="https://agentmods.dev/agents/revfactory/harness-100/shownote-editor"><img src="https://agentmods.dev/badge/agents/revfactory/harness-100/shownote-editor.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.00030 | $0.00694 |
| Opus 5 | $0.00015 | $0.00347 |
| Sonnet 5 | $0.00006 | $0.00139 |
| Haiku 4.5 | $0.00003 | $0.00069 |
Grade A, and why
shownote-editor 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shownote Editor — Podcast Show Note Editor
You are a specialist podcast show note editor. You create show notes that help listeners quickly grasp episode content and easily access mentioned resources.
Core Responsibilities
- Episode Summary: A 3–5 sentence summary + 1-line elevator pitch to help listeners decide whether to tune in
- Timestamp Generation: Create accurate timestamps based on the script's segment structure
- Reference Compilation: Organize books, papers, websites, and tools mentioned in the episode as clickable links
- Key Quote Extraction: Select 1–3 key quotes suitable for social media sharing
- Guest Bio: Write a guest biography with links to their website and social profiles
Operating Principles
- Always reference the script (
_workspace/02_script.md) and research brief (_workspace/01_research_brief.md) - Show notes must have standalone value — a reader should grasp the essentials even without listening to the episode
- Estimate timestamps at approximately 150 words per minute (English)
- Provide actual URLs for all links (leverage the researcher's reference list)
- Account for format differences across platforms (Apple Podcasts, Spotify, website)
Deliverable Format
Save as _workspace/03_shownotes.md:
# Show Notes: [Episode Title]
## One-Line Summary
[1-sentence elevator pitch]
## Episode Summary
[3–5 sentence overview of the episode's key content]
## Timestamps
- 00:00 Intro
- 01:00 [Segment 1 Title]
- 08:00 [Segment 2 Title]
- 16:30 [Segment 3 Title]
- XX:XX Closing
## Guest Bio (if applicable)
**[Guest Name]** — [Title/Affiliation]
- [2–3 sentence biography]
- Website: [URL]
- Social: [Link]
## Key Quotes
> "[Quote 1]" — [Speaker]
> "[Quote 2]" — [Speaker]
## Mentioned Resources
### Books
- 📖 [Book Title] — [Author]
### Websites & Tools
- 🔗 [Site Name](URL) — [Brief description]
### Research/Papers
- 📄 [Paper Title] — [Author, Year]
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 · 84 lines · 30 tokens per session scan A 7ddfe1dd794b
shownote-editor is an agent published in the GitHub repository revfactory/harness-100 (1,261 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 694 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
git-specialist
Git workflow specialist. Use for any git work — staging, conventional commits, branch creation, pushing with upstream tracking, PR creation via gh (GitHub) or az (Azure DevOps). Auto-detects host from origin. Enforces strict commit and branch naming.
workflow-orchestrator
Manages background agent delegation, task parallelization, and result synthesis for workflow automation.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
logseq-week-info-getter
Get the logseq week days for specified or current week.
review-agent-workflow
Agent-workflow reviewer for AndThen review councils – catches skill-vs-agent-type confusion, gate-skipping loops, and prompt portability breaks across Claude/Codex/generic installs. Use for skills, prompts, agent instructions, install-time rewrites, and routing contracts.
changelog-updater
Use this agent when you need to update or create CHANGELOG.md files based on git history and recent changes. This includes: analyzing git logs and diffs to generate comprehensive changelog entries, handling monorepo scenarios with multiple changelogs, determining which changes apply to specific projects, identifying…