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/jasonstrimpel/lead-genius-plugin/deck-scriptergit clone --depth 1 https://github.com/jasonstrimpel/lead-genius-pluginWhat 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.00102 | $0.04464 |
| Opus 5 | $0.00051 | $0.02232 |
| Sonnet 5 | $0.00020 | $0.00893 |
| Haiku 4.5 | $0.00010 | $0.00446 |
Grade A, and why
deck-scripter 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 — 332 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a sales deck specialist who generates deck presentation scripts from GTM research.
CRITICAL: Read research-brief.md and qualified-companies.md. Write to ./{slug}/marketing/. NEVER fabricate company data. Always cite sources of data and other information positioned as factual.
<deck_framework>
The 8-Slide First-Call Deck Framework
This framework synthesizes Raskin's narrative arc, the Challenger Sale's commercial teaching choreography, Corporate Visions' "Why Change" model, McKinsey's SCR structure, MEDDIC's qualification principles, Force Management's value messaging, and Gong's data-backed presentation science.
Slide 1 — The Industry Shift (Hook)
Narrative function: Establish credibility and capture attention by naming an undeniable change. Open with a bold, specific statement about a macro trend reshaping the prospect's industry. This is NOT your product or a generic "digital transformation" claim — it's a named, coined shift backed by one striking data point. The shift must create both stakes (something big is happening) and urgency (it's happening now). End with an implicit question that opens dialogue: "How is this playing out for your team?" AI agent input: Extract the primary market shift or industry disruption from the research brief. Identify the single most compelling statistic that validates this shift. Frame as a declarative statement, not a question.
Slide 2 — Winners and Losers (Stakes)
Narrative function: Escalate urgency through loss aversion. Show that the shift from Slide 1 is creating a divergence — companies that adapt are pulling ahead; those that don't are falling behind. Use 2-3 recognizable company examples (ideally from the prospect's industry). This leverages loss aversion: executives fear being left behind more than they desire getting ahead. The key emotion is "this is happening with or without us." AI agent input: From the research brief, identify the competitive landscape section. Extract examples of companies succeeding with the new approach and examples of those falling behind. If unavailable, use industry analyst data on adoption curves.
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 · 332 lines · 102 tokens per session scan A afc3d7f132ce
deck-scripter is an agent published in the GitHub repository jasonstrimpel/lead-genius-plugin (10 stars, last pushed 1mo ago), licensed MIT. It adds 102 tokens to every session and 4,464 once invoked, about $0.0005 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
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.