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 agentmods add skills/epistates/sparx/composenpx skills add Epistates/sparX --skill composegit clone --depth 1 https://github.com/Epistates/sparXWhat 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 | $0.00037 | $0.01445 |
| Opus 5 | $0.00018 | $0.00723 |
| Sonnet 5 | $0.00007 | $0.00289 |
| Haiku 4.5 | $0.00004 | $0.00145 |
Grade A, and why
compose 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 2d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compose an Algorithm-Optimized X Post
You are an expert X content strategist with deep knowledge of the Phoenix algorithm. Draft a post that maximizes predicted engagement signals.
Input
The user provides either:
- A topic or idea to write about
- A rough draft to transform into an optimized post
- A product/feature announcement to frame for maximum reach
- A URL — GitHub release page, blog post, product page, README, changelog, or any web page to compose a post about
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:
- GitHub release page → Extract version, features, benchmarks → compose an announcement post
- Blog post → Extract key insight + data → compose a post highlighting the most shareable finding
- Product/landing page → Extract value prop + metrics → compose a launch post
- GitHub README → Extract what the project does + proof points → compose an introduction post
- Changelog → Extract user-facing improvements → compose a "what's new" post
After reading the URL content, proceed to Step 1 using the extracted material as your source.
Step 1 — Understand the Goal
Identify:
- What is the core message?
- Who is the target audience?
- What format fits best? (announcement, insight, question, hot take, build-in-public)
Step 2 — Read Algorithm Context
Read these files for current optimization data:
- scoring.md — for weight hierarchy
- content-formats.md — for format-specific guidance
- penalties.md — for what to avoid
Step 3 — Draft the Post
Apply these rules in order of priority:
Hook (first 8-12 words)
- Must create curiosity, tension, or promise specific value
- No jargon in the hook unless the audience expects it
- See templates.md for proven hook patterns
What ships with it
2 files 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.
- 2d ago First seen · 143 lines · 37 tokens per session scan A 029e9158ecbf
compose is a skill published in the GitHub repository Epistates/sparX (3 stars, last pushed 5mo ago), licensed MIT. It adds 37 tokens to every session and 1,445 once invoked, about $0.0002 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
opencli-adapter-author
Use when writing an OpenCLI adapter for a new site or adding a new command to an existing site. Guides end-to-end from first recon through field decoding, adapter coding, and verify. Replaces opencli-oneshot / opencli-explorer. For ad-hoc browser driving (no adapter), see opencli-browser instead; for a top-level…
cloud
Documentation reference for using Browser Use Cloud — the hosted API and SDK for browser automation. Use this skill whenever the user needs help with the Cloud REST API (v2, v3, or v4), browser-use-sdk (Python or TypeScript), X-Browser-Use-API-Key authentication, cloud sessions, browser profiles, profile sync, CDP…
open-source
Documentation reference for writing Python code using the browser-use open-source library. Use this skill whenever the user needs help with Agent, Browser, or Tools configuration, is writing code that imports from browseruse, asks about @sandbox deployment, supported LLM models, Actor API, custom tools, lifecycle…
opencli-usage
Use at the start of any OpenCLI session — this is the top-level map of what opencli can do, how to discover adapters, what flags and output formats are universal, and which specialized skill to load next. Point here when an agent asks "what can opencli do?" or "how do I find the right command?".
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
opencli-browser-sitemap
Use when driving a website with opencli browser and sitemap context is available, requested, or needed to avoid blind navigation. Guides agents to consume site sitemap files lazily, choose adapter/browser fallback paths, resume from state signatures, and mark stale sitemap entries without trusting them over live…