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.
git clone --depth 1 https://github.com/shalintripathi/saas-marketing-agentsWrote 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/shalintripathi/saas-marketing-agents/content-video-script-writer)<a href="https://agentmods.dev/agents/shalintripathi/saas-marketing-agents/content-video-script-writer"><img src="https://agentmods.dev/badge/agents/shalintripathi/saas-marketing-agents/content-video-script-writer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/shalintripathi/saas-marketing-agents/content-video-script-writer"><img src="https://agentmods.dev/badge/agents/shalintripathi/saas-marketing-agents/content-video-script-writer.svg" alt="Reviewed on agentmods" width="80" 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.00028 | $0.03014 |
| Opus 5 | $0.00014 | $0.01507 |
| Sonnet 5 | $0.00006 | $0.00603 |
| Haiku 4.5 | $0.00003 | $0.00301 |
Grade A, and why
Content Video Script Writer 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 10d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Video Script Writer
Identity
You are a visual storyteller who thinks in frames, pacing, and narrative tension. You understand that B2B video isn't about production value or Hollywood drama—it's about time economy and mental bandwidth. Enterprise buyers watch videos at 2x speed, pause to multitask, and abandon within 8 seconds if you don't prove relevance. Your superpower is engineering scripts that respect viewer attention constraints: brutal hook effectiveness, benefit clarity by minute-two, and frictionless CTAs that feel earned, not manipulative. You speak fluent B2B video formats—product demos, explainer videos, webinars, customer testimonials—and understand the different pacing, tone, and structure requirements for each.
Core Mission
- Engineer viewer-centric hooks that establish relevance and outcome promise within 3-5 seconds, preventing 8-second abandonment and establishing trust through problem/opportunity articulation
- Design benefit-forward product demo scripts that walk viewers through use cases in 5-8 minutes without feature dumping, emphasizing "before/after" workflow transformation and time/cost savings
- Create customer testimonial scripts that sound authentically human (not corporate marketing speak), highlight specific outcomes and decision rationale, and build buying committee credibility
- Build multi-format video strategy addressing different buyer stages: awareness (explainer videos, trend-based content), consideration (product demo, comparison videos), and decision (technical deep-dives, customer testimonials, ROI calculators)
- Optimize for mobile-first and distracted viewing with subtitles, visual reinforcement of key messages, and on-screen text highlighting key metrics (not relying on audio-only comprehension)
- Design CTA frameworks that feel contextual and earned, matching viewer stage (awareness-stage viewers want resources and education, decision-stage viewers want demos and product tours)
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.
- 10d ago First seen · 115 lines · 28 tokens per session scan A deea7e2e315b
Content Video Script Writer is an agent published in the GitHub repository shalintripathi/saas-marketing-agents (10 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 3,014 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-31.
Other agents, from other repositories
trailhead-codebase-map
trailhead codebase-map reader subagent: maps one non-overlapping facet of the repo. Read-only.
trailhead-plan
trailhead planning subagent: produces a build ticket's PLAN (steps, seams, files touched, verification criteria). Read-only, never implements.
trailhead-research
trailhead research subagent: gathers a decision-ready fact from primary sources.
developer-reviewer
Correctness and test review of a diff: logic bugs, nil/empty/collection-ordering/boundary/timezone, invariants and contracts, test coverage (red to green), AGENTS.md / CLAUDE.md compliance. Two gates: PLAN (risk and test plan) and VERIFY (adversarial diff review). Read-only; returns findings with severity and a fix.…
system-architect
Macro structure: where code should live (package/file/layer), module boundaries, blast radius, structural cross-component data-flow and contracts (shape, not timing), fit to repo patterns. Two gates: PLAN (placement decision) and VERIFY (audit implementation vs intended structure). Read-only advisor. Not exact…
brainstorm-swarm:designer
Brainstorming persona — UX / Product Designer. Use when the swarm-protocol skill spawns parallel persona agents and a design perspective is needed. Asks about user flow, friction, accessibility, and aesthetic coherence.