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/social-media-studio --skill tweet-thread-buildergit clone --depth 1 https://github.com/SkillMedev/social-media-studioWrote 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/social-media-studio/tweet-thread-builder)<a href="https://agentmods.dev/skills/skillmedev/social-media-studio/tweet-thread-builder"><img src="https://agentmods.dev/badge/skills/skillmedev/social-media-studio/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/social-media-studio/tweet-thread-builder"><img src="https://agentmods.dev/badge/skills/skillmedev/social-media-studio/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.01388 |
| Opus 5 | $0.00051 | $0.00694 |
| Sonnet 5 | $0.00020 | $0.00278 |
| Haiku 4.5 | $0.00010 | $0.00139 |
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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- Tweet Thread Builder — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 106 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.
- 9d ago First seen · 106 lines · 102 tokens per session scan A 2a719d4377d7
Tweet Thread Builder is a skill published in the GitHub repository SkillMedev/social-media-studio (1 stars, last pushed 2mo ago), licensed MIT. It adds 102 tokens to every session and 1,388 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-31.
Other skills, from other repositories
Landing Page Copy
Write landing-page copy section by section - hero, social proof, features-as-benefits, objections, CTA - leading with one promise and proving it down the page. Use when someone asks "write my landing page", "improve my hero headline", "what should the homepage say", "turn these features into benefits", or is shipping…
testimonial-capture-interview
Runs customer interviews engineered to produce usable testimonials and case-study raw material - a question sequence that elicits before/after specifics and real numbers, a permission and approval workflow, quote-editing ethics (tighten but never fabricate), and a soundbite extraction procedure. Use when a user says…
Case Study Builder
Turn a customer win into a credible case study - interview-driven raw material, a challenge-solution-results arc, and a quantified results section with real customer quotes. Use when someone asks "write a case study from this customer call", "turn this win into a customer story", "what should I ask the customer in the…
Email Newsletter Pro
Write recurring email newsletters - subject lines that earn the open, preview text that extends them, a body structure readers finish, and cadence rules that keep the list healthy. Use when someone asks "write my newsletter", "give me subject line options", "why is my open rate dropping", "should I send weekly or…
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…