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/strategynpx skills add Epistates/sparX --skill strategygit 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/strategy)<a href="https://agentmods.dev/skills/epistates/sparx/strategy"><img src="https://agentmods.dev/badge/skills/epistates/sparx/strategy.svg" alt="Measured on agentmods" 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 | $0.00038 | $0.01482 |
| Opus 5 | $0.00019 | $0.00741 |
| Sonnet 5 | $0.00008 | $0.00296 |
| Haiku 4.5 | $0.00004 | $0.00148 |
Grade A, and why
strategy 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 3d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Strategy Planning
Build a comprehensive X content strategy aligned with the Phoenix algorithm and the user's goals.
Input
The user provides:
- Niche/topic area — what they post about
- Current state — follower count, typical engagement, posting frequency
- Their X profile URL or username — read their profile and recent posts directly
- Goals — growth targets, audience building, product promotion, thought leadership
- Constraints — time available, content resources, posting schedule limitations
- Timeframe — weekly plan, monthly plan, or long-term roadmap
Process
Step 0 — Read User's X Profile (if available)
If the user provides their X username or profile URL, read their profile to auto-assess current state instead of relying on self-reported data:
Use WebFetch to read https://x.com/[username] — extract bio, follower/following counts, recent post previews, and pinned post.
For deeper analysis (engagement metrics on recent posts, analytics data), suggest running /analyze recent which uses chrome for authenticated access.
This replaces the need for the user to manually report their follower count, posting frequency, and engagement levels.
Step 1 — Assess Current State
Understand where the user is:
Account Stage:
| Stage | Followers | Strategy Focus |
|---|---|---|
| Launch | 0-100 | Reply farming, community building, 1 quality post/day |
| Growth | 100-1K | Content consistency, thread expertise, niche authority |
| Scale | 1K-10K | Content pillars, collaborations, repurposing pipeline |
| Authority | 10K+ | Thought leadership, selective posting, community building |
Content Audit:
- What formats have they tried?
- What's worked best? (ask for data or review)
- What's their authentic voice/personality?
- What unique knowledge or experience do they have?
Step 2 — Define Content Pillars
Every account needs 3-5 content pillars — recurring themes the audience expects:
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.
- 3d ago First seen · 161 lines · 38 tokens per session scan A da05f93015cd
strategy is a skill published in the GitHub repository Epistates/sparX (3 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 1,482 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
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work.
opencli-autofix
Automatically fix broken OpenCLI adapters when commands fail. Load this skill when an opencli command fails — it guides you through collecting a trace artifact, patching the adapter, retrying, and filing an upstream GitHub issue after a verified fix. Works with any AI agent.
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…