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 hooksgit 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/hooks)<a href="https://agentmods.dev/skills/epistates/sparx/hooks"><img src="https://agentmods.dev/badge/skills/epistates/sparx/hooks/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/hooks"><img src="https://agentmods.dev/badge/skills/epistates/sparx/hooks.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.00035 | $0.00797 |
| Opus 5.5 | $0.00014 | $0.00319 |
| Sonnet 5.5 | $0.00007 | $0.00159 |
| Haiku 4.5 | $0.00003 | $0.00080 |
Grade A, and why
hooks 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Scroll-Stopping Hooks
The first 8-12 words of an X post determine whether anyone reads the rest. Generate multiple high-impact hook options optimized for the Phoenix algorithm's dwell time signal.
Input
The user provides:
- A topic they're posting about
- A rough idea of the post content
- An existing hook they want alternatives for
- A URL — read the content via WebFetch to understand the subject, then generate hooks based on the actual material (see ../../../reference/url-reading.md)
Process
Step 1 — Understand the Content
What is the core message? Who is the audience? What emotion should the hook trigger?
Step 2 — Read Hook Patterns
Read patterns.md for the full hook pattern library.
Step 3 — Generate 7-10 Hooks
Generate hooks across multiple pattern categories:
- Curiosity Gap — Creates an information gap the reader must fill
- Specific Number — Leads with a concrete, impressive metric
- Contrarian — Challenges conventional wisdom
- Pain Point — Names a frustration the audience feels
- Before/After — Shows transformation in minimal words
- Social Proof — Leads with credibility markers
- Question — Poses something the reader can't ignore
For each hook:
- Keep to 8-12 words (the visible preview before truncation)
- Test: Would this stop YOUR scroll?
- Ensure it's honest — don't promise what the post doesn't deliver
Step 4 — Rank and Annotate
Rank all hooks by predicted effectiveness and annotate:
- Best for dwell — which hook will make people read the full post?
- Best for replies — which hook triggers an urge to respond?
- Best for bookmarks — which hook signals "save-worthy" content?
- Safest — which hook has lowest negative signal risk?
- Boldest — which hook has highest ceiling but more risk?
Step 5 — Output
Present all hooks in a scored table, ranked by Phoenix Score. The score represents what a full post would score with that hook (assuming a solid body + CTA):
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 · 78 lines · 35 tokens per session scan A b95fa410dfb0
hooks is a skill published in the GitHub repository Epistates/sparX (3 stars, last pushed 6mo ago), licensed MIT. It adds 35 tokens to every session and 797 once invoked, about $0.0001 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…