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 repurposegit 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/repurpose)<a href="https://agentmods.dev/skills/epistates/sparx/repurpose"><img src="https://agentmods.dev/badge/skills/epistates/sparx/repurpose/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/repurpose"><img src="https://agentmods.dev/badge/skills/epistates/sparx/repurpose.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.00052 | $0.01058 |
| Opus 5.5 | $0.00021 | $0.00423 |
| Sonnet 5.5 | $0.00010 | $0.00212 |
| Haiku 4.5 | $0.00005 | $0.00106 |
Grade A, and why
repurpose 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repurpose Content Across X Formats
Maximize content ROI by transforming a single piece of content into multiple algorithm-optimized formats for X.
Input
The user provides:
- Source content: A post, thread, blog post, README, changelog, talk transcript, or any text
- A URL — blog post, GitHub page, documentation, article, or any web page to repurpose into X content
- Target format (optional): If not specified, suggest the best transformations
URL Resolution
If the input contains a URL, read its content first using WebFetch. See ../../../reference/url-reading.md for tool selection and extraction prompts. Then proceed with the extracted content as your source material.
Transformations Available
Post → Thread
Expand a single high-performing post into a deep-dive thread:
- Use the post's core insight as the thread hook
- Break the supporting points into individual tweets
- Add proof/examples that didn't fit in the original
- Add a CTA closer
- Read ../thread/structures.md for structure patterns
Thread → Post
Distill a thread into a single punchy post:
- Extract the single most shareable insight
- Compress proof into one line
- Add a hook and reply trigger
- Good for re-posting thread content weeks later
Blog Post / README → Thread
Transform long-form content into X threads:
- Identify the 5-7 most compelling points
- Lead with the most surprising finding
- Translate written style to X conversational style
- Add visual suggestions for screenshots from the content
- Remove all links (save for reply)
Changelog / Release → Announcement Post
Transform a technical changelog into an engaging announcement:
- Lead with the user benefit, not the feature name
- Add a specific benchmark or comparison
- Frame in terms of the audience's workflow
- Remove internal jargon
- Read ../compose/templates.md for announcement templates
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 · 109 lines · 52 tokens per session scan A e1b086fb60c6
repurpose is a skill published in the GitHub repository Epistates/sparX (3 stars, last pushed 6mo ago), licensed MIT. It adds 52 tokens to every session and 1,058 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…