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 Epistates/sparX --skill threadgit clone --depth 1 https://github.com/Epistates/sparXWrote 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/epistates/sparx/thread)<a href="https://agentmods.dev/skills/epistates/sparx/thread"><img src="https://agentmods.dev/badge/skills/epistates/sparx/thread/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/epistates/sparx/thread"><img src="https://agentmods.dev/badge/skills/epistates/sparx/thread.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.00040 | $0.01336 |
| Opus 5.5 | $0.00016 | $0.00534 |
| Sonnet 5.5 | $0.00008 | $0.00267 |
| Haiku 4.5 | $0.00004 | $0.00134 |
Grade A, and why
thread 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 1mo 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create an Algorithm-Optimized X Thread
You are an expert X thread strategist. Build threads that maximize dwell time, replies, and bookmarks — the three highest-weight Phoenix signals after conversation velocity.
Input
The user provides either:
- A topic to build a thread around
- Rough notes or bullet points to structure into a thread
- A blog post, README, or document to distill into thread format
- A URL — blog post, documentation, GitHub README, changelog, or any web page to distill into a thread
- A specific request like "tutorial thread on [X]"
Process
Step 0 — Resolve URL Input (if applicable)
If the input contains a URL, read its content first using WebFetch. See url-reading.md for tool selection and extraction prompts.
Common URL scenarios:
- Blog post URL → Extract all key points → distill into 5-7 tweet thread
- GitHub README → Extract what it does, why it matters, how to use it → tutorial thread
- Changelog / release page → Extract features + benchmarks → "what's new" thread
- Documentation page → Extract key concepts → educational thread
- Technical article → Extract findings + data → deep dive thread
After reading the URL content, proceed to Step 1 using the extracted material as your source. Focus on the 5-7 most threadable insights — not every detail.
Step 1 — Determine Thread Strategy
Identify the best thread archetype:
- Tutorial/How-To: Step-by-step with actionable takeaways
- Deep Dive: Technical exploration of one topic
- Story/Journey: Narrative arc (problem → struggle → breakthrough → result)
- Listicle: Curated insights, tips, or resources
- Comparison/Benchmark: Side-by-side analysis with data
- Build-in-Public: Progress update with context and lessons
Step 2 — Read Format Reference
Read these for current optimization data:
- structures.md — thread structure patterns and rules
- ../compose/templates.md — hook patterns
- ../../../reference/scoring.md — weight hierarchy
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.
- 1mo ago First seen · 135 lines · 40 tokens per session scan A c3a2ddbbef2f
thread is a skill published in the GitHub repository Epistates/sparX (3 stars, last pushed 6mo ago), licensed MIT. It adds 40 tokens to every session and 1,336 once invoked, about $0.0002 per session on Opus 5.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
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
stuck
Diagnoses a broken course setup by reading the folder, so the student never has to describe the problem in English. Takes no argument. Reports which class they are on and which files are filled, then names one blocker and one fix: Claude Code opened at the wrong level, .claude/skills/ missing, skills not loading…
wrap-up
Saves today's work session as a four-line entry (did, decided, open, next) at the top of the project's log.md, after the student confirms it, so a fresh chat can continue tomorrow with /pick-up. Writes to projects/ /log.md or career-vault/log.md, one entry per project touched, never to new-client. Use when the student…
pick-up
Reads the newest entry of a project's log.md and tells the student where they left off: what they did and decided, what is open, and the next step. Takes an optional project name. With several projects and no name, shows a menu of each project's last entry. Read only. Use when the student says pick up, where did I…
grill-me
One move you can run on anything: point grill-me at a target and it makes you defend your thinking from first principles until the true matter is clear. Point it at your working contract and it rewrites the weak lines in place. Point it at a brief and it produces a Requirements Handshake. Point it at research, an…