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 assafkip/kipi-system --skill headline-engineeringgit clone --depth 1 https://github.com/assafkip/kipi-systemWrote 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/assafkip/kipi-system/headline-engineering)<a href="https://agentmods.dev/skills/assafkip/kipi-system/headline-engineering"><img src="https://agentmods.dev/badge/skills/assafkip/kipi-system/headline-engineering.svg" alt="Measured on agentmods" 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.00122 | $0.01079 |
| Opus 5 | $0.00061 | $0.00540 |
| Sonnet 5 | $0.00024 | $0.00216 |
| Haiku 4.5 | $0.00012 | $0.00108 |
Grade A, and why
headline-engineering 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 yesterday.
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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Headline Engineering
This skill fires whenever someone is writing or reviewing copy that has to earn a click.
It does NOT replace [[assaf-voice]] — voice DNA still applies. This skill handles the part voice doesn't: WHERE the copy will live and HOW that platform's audience decides what to click.
Load order
- Always load
references/platform-hooks.md— the 6 viral patterns, char-count sweet spots, first-7-words rule. - For specific platforms load
references/headline-templates.md— proven shapes per platform with char counts. - For challenges or updates load
references/research-receipts.md— the source data behind every claim in this skill.
The decision tree
Apply in order:
Step 1 — Identify the platform. Different platforms have different optimal lengths and reward different shapes. Don't write a "headline" abstractly. Write for X, OR for Reddit, OR for LinkedIn, OR for Medium. The same idea gets phrased four different ways.
Step 2 — Identify the length range.
- X: under 110 chars, sweet spot 71-100
- Reddit text titles: 30-66 chars
- LinkedIn long-form titles: 60-100 chars
- Medium titles: 50-90 chars
Step 3 — Pick the pattern. Six patterns earn clicks (full detail in references/platform-hooks.md):
- A. Absurd-concrete-object ("Real LLM on a Game Boy Color")
- B. Confession + reversal ("I'm done with X")
- C. PSA / "admits" exposé ("Anthropic admits X")
- D. Specific number + impossible feat ("64-year-old problem solved")
- E. Naive question ("Forgive my ignorance but how is X better than Y?")
- F. "I asked X to..." setup ("I asked ChatGPT to imagine itself in retirement")
Step 4 — Front-load the punch. First 5-7 words decide whether anyone reads word 8. If the punch is "21-byte file," "21" goes in the first 7 words, not at the end.
Step 5 — Run the check. Three quick tests:
- Word 7 test: cover everything after word 7. Does the hook still stop the scroll?
- Specificity test: are there at least one specific number, name, or concrete object in the first 10 words?
- Pattern test: which of A-F is this? If you can't name one, it's a generic AI-style title. Rewrite.
What ships with it
3 files 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.
- yesterday Changed b709ab36c168
- 9d ago First seen · 86 lines · 122 tokens per session scan A 67307c2c82a7
headline-engineering is a skill published in the GitHub repository assafkip/kipi-system (110 stars, last pushed today), licensed MIT. It adds 122 tokens to every session and 1,079 once invoked, about $0.0006 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
core
This skill should be used when the user says "capture memory", "save to memory", "remember this", or trigger phrases like: "I've decided", "let's use", "we're going with", "I learned", "turns out", "TIL", "discovered", "I'm stuck", "blocked by", "always use", "never do", "convention is". Also triggers on recall…
custodian
Memory system custodian for health checks, validation, and maintenance. Trigger phrases: "check memory health", "validate memories", "fix broken links", "update decay", "relocate memories", "audit memories", "memory maintenance", "custodian", "memory health".
format
MIF Level 3 specification, memory templates, and formatting guidelines.
ontology
Ontology-based entity discovery and validation for mnemonic memories. Define custom namespaces, entity types, traits, and relationships. Triggers: "entity discovery", "validate ontology", "define namespaces", "resolve entity references", "list ontologies", "show namespaces", "entity types", "entity relationships"…
search
This skill should be used when the user says "search memories", "find in memories", "grep mnemonic", "look for memory", "deep search", "synthesize knowledge", or asks questions like "what do we know about X". Provides progressive disclosure and enhanced iterative search with synthesis.
blackboard
Cross-session handoff, persistent context via blackboard, and agent coordination patterns.