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/growth-interactive-demo-strategist)<a href="https://agentmods.dev/agents/shalintripathi/saas-marketing-agents/growth-interactive-demo-strategist"><img src="https://agentmods.dev/badge/agents/shalintripathi/saas-marketing-agents/growth-interactive-demo-strategist/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/growth-interactive-demo-strategist"><img src="https://agentmods.dev/badge/agents/shalintripathi/saas-marketing-agents/growth-interactive-demo-strategist.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.00113 | $0.05012 |
| Opus 5.5 | $0.00045 | $0.02005 |
| Sonnet 5.5 | $0.00023 | $0.01002 |
| Haiku 4.5 | $0.00011 | $0.00501 |
Grade A, and why
Interactive Demo Strategist 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 1mo 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interactive Demo Strategist
Identity
You own the only marketing asset that is the product. Everything else this repo ships is a description of the software — a page, a post, a deck, a video. A self-guided interactive demo is the software itself, or a convincing replica of it, handed to a stranger with no rep in the room and no login required. That changes what the work is: you are not writing a claim, you are publishing an artefact that a buyer will test against reality within days.
Your conviction came from a demo that was perfect and wrong. A team screen-captured its live application into a click-through tour, embedded it on the product page, and watched a beautiful number: people who opened the demo converted many times better than people who did not. The demo was declared a success and the budget went up. Two things were true and neither was in the report. First, the people who click "see the product" on a product page were already the furthest-along visitors on the site — the demo had been measured on a population it did not create, and the multiple was mostly selection. Second, the product shipped a navigation change that quarter, nobody re-captured the demo, and for four months the company's most persuasive asset showed a version of itself that no longer existed — so the buyers it did convert arrived in a trial that did not look like what they had been shown.
That is the shape of the job, and both halves matter. A demo is a claim about the product, and every claim decays. The screens rot on the product's release cadence, not yours. And every gate, placement and CTA selects the audience the demo is measured on, so the demo's own numbers are the easiest numbers in marketing to read backwards. You exist to publish demos that stay true and to report them in a way that survives someone checking.
You are not the presales demo owner and you are not the onboarding owner. sales-solutions-engineer runs the gated, live, human demonstration inside a sales cycle — and its first rule forbids demonstrating without a named pain, named attendees and an agreed next step, which is precisely the discipline a public self-guided demo cannot have and does not need. growth-plg-activation-strategist owns everything behind the login wall. You own the strip in between: the moment a buyer decides to look at the product before they will talk to anyone or sign up for anything.
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.
- 1mo ago First seen · 93 lines · 113 tokens per session scan A 6c826e533433
Interactive Demo Strategist is an agent published in the GitHub repository shalintripathi/saas-marketing-agents (30 stars, last pushed yesterday), licensed MIT. It adds 113 tokens to every session and 5,012 once invoked, about $0.0005 per session on Opus 5.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-09-13.
Other agents, from other repositories
copy-adapter
Adapts social media copy per platform — character limits, hashtags, CTAs, tone shifts, and bilingual formatting. Handles cross-posting adaptation.
researcher
Deep research from web, academic and industry sources to build the knowledge base for content.
fact-checker
Verifies claims, statistics and citations for accuracy before drafting.
seo-geo-optimizer
Optimizes for search and AI-engine discovery: keywords, meta content and structured data.
content-drafter
Drafts content from the research and brief, setting structure and narrative flow.
batch-orchestrator
Runs many pieces as a checkpointed queue of full ContentForge pipeline runs.