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 SkillMedev/content-marketing-engine --skill tweet-thread-buildergit clone --depth 1 https://github.com/SkillMedev/content-marketing-engineWrote 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/skillmedev/content-marketing-engine/tweet-thread-builder)<a href="https://agentmods.dev/skills/skillmedev/content-marketing-engine/tweet-thread-builder"><img src="https://agentmods.dev/badge/skills/skillmedev/content-marketing-engine/tweet-thread-builder/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/skillmedev/content-marketing-engine/tweet-thread-builder"><img src="https://agentmods.dev/badge/skills/skillmedev/content-marketing-engine/tweet-thread-builder.svg" alt="Reviewed on agentmods" width="80" 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.00102 | $0.01398 |
| Opus 5.5 | $0.00041 | $0.00559 |
| Sonnet 5.5 | $0.00020 | $0.00280 |
| Haiku 4.5 | $0.00010 | $0.00140 |
Grade A, and why
tweet-thread-builder 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 17d 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.
This is a copy
100% identical to tweet-thread-builder — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tweet Thread Builder
Threads live or die on the first post: 90%+ of potential readers see only the hook, so a mediocre hook wastes every good post behind it. The costly mistake is spreading one thin idea across fifteen posts or burying the payoff behind "a thread 🧵" with no substance. Earn each scroll.
Operating procedure
Step 1: Gather inputs
- The single idea or story - one sentence. If the user gives several, pick the one with the most concrete specifics (numbers, names, before/after); park the rest.
- The payoff for the reader: what they know or can do after reading.
- Proof material: numbers, screenshots, examples. A thread without at least two concrete specifics is an opinion, not a thread - send the user back for material.
- The one CTA (default: follow; alternatives: a link, or "reply with your version").
Label any number the user estimates as an estimate.
Step 2: Write the hook (post 1) - and an A/B pair
- Promise a specific payoff: a number, a transformation, a contrarian take.
- No preamble. The first line is the whole pitch. Keep the hook under 200 characters - dense hooks read as work.
- Proven patterns: "I did X for N days. Here's what happened." / "Everyone believes X. They're wrong." / "N lessons from [hard thing]:"
Always draft two hooks with different mechanisms so the user can pick or test:
- A (curiosity/story): "I deleted 80% of our landing page. Signups went up 34%. What we removed:"
- B (contrarian/claim): "Long landing pages are killing your signups. We cut ours to one screen and grew 34%. Proof:"
Same material, different bet: A sells the mystery of what was removed; B sells the argument. Pick A for story-driven audiences, B when the take itself is polarizing enough to drive replies.
Step 3: Outline the beats
- One idea per post. If a post has two ideas, split it. If two posts share one idea, merge them.
- 5-12 posts is the sweet spot. Under 5, make it a single tweet; over 12, cut - every post past 12 sheds readers faster than it adds value.
- Order the beats so each ends on a small open loop that the next post resolves; momentum is the structure.
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.
- 17d ago Changed · +2 lines 407b29d9aabc
- 1mo ago First seen · 106 lines · 102 tokens per session scan A 2a719d4377d7
tweet-thread-builder is a skill published in the GitHub repository SkillMedev/content-marketing-engine (1 stars, last pushed 17d ago), licensed MIT. It adds 102 tokens to every session and 1,398 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to tweet-thread-builder, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
linkedin-post-writer
Write LinkedIn posts built for the feed - a hook that survives the two-line truncation, scannable one-idea-per-line structure, a comment-bait close, and first-hour engagement moves. Use when someone asks "write a LinkedIn post about this", "punch up my LinkedIn hook", "why did my post get no reach", or "turn this win…
tweet-thread-builder
Turn one idea into a tight tweet thread - a hook that earns the click, one beat per post, and momentum to a single CTA. Use when someone asks "turn this into a thread", "write a thread about my launch", "why did my thread flop", or "give me hook options for this". Do NOT use for LinkedIn-format posts - use…
social-caption-writer
Write one platform-native caption from a topic and brand voice, with a front-loaded hook, native length, and a single earned CTA. Use when the user gives a topic (and optionally brand voice or a described image/video) and asks for an Instagram, LinkedIn, X/Twitter, or TikTok caption. Do NOT use when the user wants a…
social-content-calendar
Builds a 4-week multi-platform posting calendar for a brand or social team, balancing content pillars, per-channel cadence, and real key dates into a week-by-week grid. Use when the user asks to plan, build, or audit a social content calendar or posting schedule across multiple channels (LinkedIn, X, Instagram…
social-hook-generator
Generates 10 labeled opening lines for a written social post, one per hook archetype, so the writer can test instead of guess. Use when drafting or rewriting the first line of a LinkedIn post, X post or thread, Instagram caption, or newsletter intro. Do NOT use when the hook is the spoken or on-screen opener of a…
hashtag-strategist
Builds a tiered hashtag and keyword set sized to the account's actual reach - mixing broad, niche, and branded tags per platform limits and screening out banned, spammy, or shadow-flagged tags. Use when someone asks "what hashtags should I use", "build me a hashtag set for this post", "audit my tag block", or is…