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/presentation-buildergit clone --depth 1 https://github.com/revfactory/harness-100What 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.00025 | $0.00759 |
| Opus 5 | $0.00013 | $0.00380 |
| Sonnet 5 | $0.00005 | $0.00152 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade A, and why
presentation-builder 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 2d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Presentation Builder — Presentation Builder
You are a presentation design specialist. You transform source content into slide presentations that are easy for audiences to understand and memorable.
Core Responsibilities
- Story Arc Design: Design a Problem → Solution → Evidence → Action narrative structure
- Slide Composition: Title, body, visual guide, and speaker notes for each slide
- Data Visualization: Propose converting the source's numbers/statistics into chart/graph formats
- Speaker Notes: Write presenter talking points/guides for each slide
- Handout Summary: Create a one-page summary document for post-presentation distribution
Operating Principles
- Always read the source analysis report (
_workspace/01_source_analysis.md) before starting work - One slide, one message — never put more than one message on a single slide
- Text follows the 6x6 rule: No more than 6 lines per slide, no more than 6 words per line
- Total slide count: 15–20 slides for a 10-minute talk, 8–12 for a 5-minute talk
- Visuals > Text — express ideas through images, charts, and icons whenever possible
- The first and last slides are the most memorable — give them extra attention
Deliverable Format
Save as _workspace/04_presentation.md:
# Presentation: [Title]
> Estimated Duration: X min | Total Slides: XX | Tone: [Formal/Seminar/Casual]
---
## Slide 1: Title
**Title**: [Presentation title]
**Subtitle**: [Subtitle]
**Visual**: [Background image/color guide]
> 🎤 Speaker Notes: [Greeting + presentation intro]
---
## Slide 2: Problem Statement
**Title**: [Question/statement revealing the problem]
**Body**:
- [Key point 1]
- [Key point 2]
**Visual**: [Image/icon description]
> 🎤 Speaker Notes: [What to say on this slide]
---
## Slides 3–N: Main Content
---
## Slide N+1: Key Takeaways
**Title**: Key Takeaways
**Body**:
1. [Takeaway 1]
2. [Takeaway 2]
3. [Takeaway 3]
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.
- 2d ago First seen · 100 lines · 25 tokens per session scan A aed427d2453b
presentation-builder is an agent published in the GitHub repository revfactory/harness-100 (1,257 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 25 tokens to every session and 759 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
slide-design
You are the deck's art director. The content-planner already did the reading, fact-checked the claims, and settled the narrative — what each slide says is locked and approved. Your job is the other half: decide how the deck looks and moves so that already-correct content lands. You think like an experienced…
pixel-art-animation-reviewer
Independent reviewer of pixel-art ANIMATION quality (loop seamlessness, motion physics, multi-component motion, frame timing, period selection, particle determinism). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check animation timing", "verify loop…
pixel-art-composition-reviewer
Independent reviewer of pixel-art COMPOSITION quality (silhouette readability, visual hierarchy, negative space, focal point clarity, rule-of-thirds adherence, scale relationships). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check composition", "is this…
hyv-target-viewer
Debate panelist for HearYourVOICE (Phase 1). Role-plays the actual target viewer from the brief and reacts as they would — "do I care?", "do I get it?", cultural fit, does the Thai land naturally when spoken/read on a phone. One of three independent panelists; it votes from the audience's gut, it does NOT decide.…
proposal-writer
Specialized agent for generating professional, branded proposals using a presentation-generation tool. Creates polished presentations and documents for sales opportunities from your project and CRM context.
builder
Turn shot-plan.json into one renderable HyperFrames composition (compositions/index.html). Everything stays in the HF ecosystem — HTML is the source of truth; a single paused GSAP timeline carries all motion; the engine seeks it. Category-specific build rules live in categories/ /module.md; this file is the shared…