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 jtsternberg/claude-plugins --skill headline-refinergit clone --depth 1 https://github.com/jtsternberg/claude-pluginsWrote 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/jtsternberg/claude-plugins/headline-refiner)<a href="https://agentmods.dev/skills/jtsternberg/claude-plugins/headline-refiner"><img src="https://agentmods.dev/badge/skills/jtsternberg/claude-plugins/headline-refiner.svg" alt="Measured on agentmods" 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.00018 | $0.00441 |
| Opus 5 | $0.00009 | $0.00220 |
| Sonnet 5 | $0.00004 | $0.00088 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
headline-refiner 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 8d 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.
What it actually says
Headline Refiner
Transform weak headlines into compelling ones using the 5-Part Headline Framework.
Quick Example
Before: "Writing Tips" After: "7 writing habits that helped me publish 300 articles in 2 years"
Workflow
Step 1: Analyze the Current Headline
Identify which of the 5 components are present or missing:
- Number — How many things promised?
- What — Is the topic clear?
- Who — Is the audience explicit or implied?
- Why — Is there a positive or negative outcome?
- Twist — Are additional outcomes stacked?
For detailed guidance on each component, see references/framework-guide.md.
Step 2: Clarify the Content
Before refining, understand:
- What exactly is the reader getting?
- Who is the ideal reader?
- What outcome do they want? What do they want to avoid?
Step 3: Generate Refined Options
Produce 3-5 headline variations. Include at least:
- One with explicit audience naming
- One with positive outcome framing
- One with negative outcome framing
- One that "twists the knife" with stacked outcomes
Step 4: Validate and Recommend
Verify each option against the checklist in references/framework-guide.md. Select the strongest based on:
- Clarity (if confused, reader is gone)
- Specificity (concrete > vague)
- Relevance to target audience
- Platform constraints (if applicable)
Platform Constraints
When space is limited, prioritize in this order:
- What (always required—clarity is non-negotiable)
- Number (helps set expectations)
- Who (if building an audience, name them)
- Why (positive or negative outcome)
- Twist (only if space allows)
YouTube Shorts: ~6 words | Email subjects: ~9 words | Full headlines: no limit
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 62 lines · 18 tokens per session scan A fe8dddbc8918
headline-refiner is a skill published in the GitHub repository jtsternberg/claude-plugins (5 stars, last pushed 3d ago), licensed MIT. It adds 18 tokens to every session and 441 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…