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 headline-as-claimgit 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/headline-as-claim)<a href="https://agentmods.dev/skills/kalyvask/winning-writing/headline-as-claim"><img src="https://agentmods.dev/badge/skills/kalyvask/winning-writing/headline-as-claim/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/headline-as-claim"><img src="https://agentmods.dev/badge/skills/kalyvask/winning-writing/headline-as-claim.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00135 | $0.01884 |
| Opus 5 | $0.00068 | $0.00942 |
| Sonnet 5 | $0.00027 | $0.00377 |
| Haiku 4.5 | $0.00014 | $0.00188 |
Grade A, and why
headline-as-claim 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Headline as claim
Source: Josh Constine's Fundraising Guide ("punchy slide titles that tell the story of each slide, not just 'Product' or 'Market'") + Katie Kingsbury / NYT Opinion's headline rules + the existing op-ed-coach headline guidance.
The premise
Most documents are built on category labels:
"Product" / "Market" / "Team" / "Why Now" / "Background" / "Conclusion"
These titles waste eye-time. The reader sees "Market" and learns nothing — they have to read the section to find out what the market claim is. A claim title, by contrast, IS the section if scanned.
"Our AI cuts notarization time 85%" (Constine example) "Olympians earn the IOC billions. Guess who the IOC almost never pays." (Kristof headline) "$14B in U.S. recall costs come from connector-seating failures."
A document with claim-titles is scannable. A reader who reads only the titles still gets the argument. A reader who reads the body gets the evidence. Both are served.
Where this applies
- Pitch deck slide titles (Constine's original case)
- Pitch memo section headings
- Op-ed headlines (NYT Opinion bar)
- Substack post titles (decides clickthrough)
- Email subject lines (decides open rate)
- Memo section headings (decides whether the boss reads past page 1)
- Chapter titles in long-form
- Performance-review section headings
The same rule everywhere: a title earns its place by making a claim, not by labeling a category.
The four types of bad titles
1. Pure category labels
"Product." "Market." "Background." "About Us." The reader's brain registers "section coming" and moves on. Wasted real estate.
2. Generic descriptions
"How AI is transforming education." "Some thoughts on Olympic compensation." "An overview of our Q3." Better than labels, still forgettable. No specific claim, nothing arguable.
3. Question titles
"Is AI overhyped?" / "What's wrong with healthcare?" Sometimes works, more often dodges. A question lets the writer avoid committing. Replace with the answer.
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 · 169 lines · 135 tokens per session scan A b82263ac1ae7
headline-as-claim is a skill published in the GitHub repository kalyvask/winning-writing (13 stars, last pushed 6d ago), licensed MIT. It adds 135 tokens to every session and 1,884 once invoked, about $0.0007 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
domain
When you want to brainstorm and check available .com domains for a new project — brand naming, aftermarket pricing (HugeDomains / Afternic / Sedo / Dan), USPTO trademark screening, and social handle availability. Built on Laura Roeder's "work backwards from availability, not from a name you fell in love with"…
company-brain
Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so Claude can answer questions on your team's behalf. Team-scope sibling to second-brain (which is personal-scope). Seven modes — capture (drop something into the right structured dir), compile (process into wiki…
slide-deck
When you want to draft, update, convert, or export a slide deck for a React/Next.js slide system (${SLIDEDECKREPO:-$HOME/code/your-slide-deck-site}/src/app/slides/). Writes TypeScript Slide[] arrays using your primitives (Eyebrow, Heading, Accent, Body, BulletList, Divider, TwoCol, GradientText), 12 cycling brand…
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
session-cleanup
Identify stale and empty Claude Code sessions in the Agent Monitor and explain the cleanup endpoint (POST /api/settings/cleanup), always showing the exact list of what WOULD be removed before anything is deleted. Cleanup permanently deletes data, so this skill previews first and requires explicit user confirmation.…
suede-onboarding
Suede-affiliated onboarding and activation strategy for first-run sequencing, empty states, setup checklists, activation milestones, time to value, and retention-linked measurement. Use when users sign up but fail to reach first value or the product needs a new first-session flow. NOT FOR: registration optimization…