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 skills add kalyvask/winning-writing --skill pitch-memogit clone --depth 1 https://github.com/kalyvask/winning-writingWrote 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/skills/kalyvask/winning-writing/pitch-memo)<a href="https://agentmods.dev/skills/kalyvask/winning-writing/pitch-memo"><img src="https://agentmods.dev/badge/skills/kalyvask/winning-writing/pitch-memo/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/skills/kalyvask/winning-writing/pitch-memo"><img src="https://agentmods.dev/badge/skills/kalyvask/winning-writing/pitch-memo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 190 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00106 | $0.02191 |
| Opus 5 | $0.00053 | $0.01095 |
| Sonnet 5 | $0.00021 | $0.00438 |
| Haiku 4.5 | $0.00011 | $0.00219 |
Grade A, and why
pitch-memo 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 11d 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pitch memo
Source: Josh Constine's Fundraising & Pitch Deck Guide — specifically his 15-question memo template — plus Kramon's BLUF rule, Konrad's "tell me a secret about the future," and the existing pitch-coach framework.
Why a memo (not a deck)
For pre-seed and seed companies, a memo can outperform a deck:
- No design wrangling. No fiddling with slide layouts or hiring a designer.
- Pretty design can hide weak thinking; a memo can't. If the founder can't write the 15 answers cleanly, they're not ready to pitch.
- It's the deck script. Even if you eventually build a deck, the memo is the narrative spine — write it first, design slides to support it, not the other way around.
- Decks leave investors with questions; memos answer them upfront. Less follow-up email cycle.
A memo replaces a deck for: pre-seed, founders who think in text more than imagery, and any raise where you're competing on substance over presentation. A memo complements a deck for everyone else.
The 15 questions (Constine)
Every investor asks the same 15 things. A memo that answers all of them in order is the most efficient possible pitch artifact.
1. Company name
Ideally, if you hear it you can spell it; if you read it you can pronounce it. You should be the top Google or App Store result for your name + a relevant keyword.
2. Tagline
One-line description. Plain English. No buzzwords. "AI co-pilot for notaries." / "Forward-deployed engineers, but as software." / "Stripe for healthcare data."
3. Problem
- What's wrong with the world?
- How acute is the pain?
- Who specifically has it? (A must-have for a small niche beats a nice-to-have for a wide market.)
- Show emotional resonance — your own first-customer story or a named person's story, not abstractions.
4. Solution
- Core functionality of the product
- How did you come up with it (origin story matters)
- How does it make a few people's lives a lot better, or a lot of people's lives a little better?
- One screenshot or a short demo video walking the most common use case
- Why is this exponentially better, not linearly better?
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.
- 11d ago First seen · 191 lines · 106 tokens per session scan A a3bc05a63211
pitch-memo is a skill published in the GitHub repository kalyvask/winning-writing (13 stars, last pushed 6d ago), licensed MIT. It adds 106 tokens to every session and 2,191 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-30.
Other skills, from other repositories
project-memory
Generate a project-specific context file from a brief so an AI assistant remembers your editorial constraints, voice, audience, and quality bar across sessions.
project-retrospective
Generate a LESSONS.md from a finished project: what worked, what didn't, what to reuse, what to retire — formatted for next-project carry-over.
template-selector
Recommend the right skill bundle, agent, and workflow sequence for a new project — so media professionals can start producing instead of browsing a 394-skill library.
multi-author-harmonizer
Reviews a text written or assembled by multiple authors and produces a detailed inconsistency report — flagging voice shifts, terminology mismatches, tonal clashes, and formatting discrepancies — with specific harmonisation recommendations for each.
jargon-flagger
Scans a draft and flags every instance of technical jargon, unexplained acronyms, and insider language that a general-audience reader would not understand — with a plain-language alternative for each.
passive-voice-checker
Identifies every passive-voice construction in a draft, assesses whether each weakens or serves the prose, and offers active-voice alternatives for those that should be changed — while leaving justified passives alone.