test

A setup-checking skill for sparX, the coding-agent environment described in its project files. It checks required files, available skills, and whether a sample content command works.

In plain words
What is it for?
Use it to verify an installation, troubleshoot setup issues, count discovered skills, and run a quick content-pipeline check.
Why use it?
It helps find missing files, unavailable skills, or broken setup before they cause larger problems.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/epistates/sparx/test
Any agent
npx skills add Epistates/sparX --skill test
Clone the repo
git clone --depth 1 https://github.com/Epistates/sparX

Made for: Claude Code, Codex.

Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 813 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00028 $0.00813
Opus 5 $0.00014 $0.00407
Sonnet 5 $0.00006 $0.00163
Haiku 4.5 $0.00003 $0.00081

Measured 2d ago against content hash 12136c8dbba8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

test 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.

.claude/skills/test/SKILL.md · 125 lines

How it starts

The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Test sparX Setup

Quick verification that everything is wired up correctly. Runs a series of checks and reports status.

Process

Run all checks (or a subset if the user specifies). Present results as a checklist.

1. Core Setup

✅ / ❌  CLAUDE.md loaded — check that Phoenix algorithm context is available
✅ / ❌  Reference docs exist — check reference/scoring.md, reference/penalties.md, etc.
✅ / ❌  Skills discovered — list all skills Claude can see (should be 15)

How to verify:

  • Read CLAUDE.md and confirm it contains "Phoenix Algorithm"
  • Check that reference/scoring.md exists
  • List available skills and count them

2. Skill Smoke Test

Run a quick /hooks generation to prove the content pipeline works:

Generate 3 hooks for: "a new open-source developer tool"

Pass criteria:

  • Produces 3 distinct hooks
  • Each is under 280 characters
  • No engagement bait phrases
  • Phoenix Score block appears
✅ / ❌  Skill pipeline — /hooks produced scored output

3. Remotion (optional)

Check if the Remotion project exists:

ls marketing/remotion.config.ts 2>/dev/null
✅ / ❌  Remotion project — marketing/ directory with remotion.config.ts
✅ / ❌  Remotion skills — marketing/.claude/skills/remotion-best-practices/SKILL.md
✅ / ❌  Tailwind configured — marketing/tailwind.config.ts or similar

If not installed:

⬜  Remotion not installed — run: pnpm create video --blank marketing

4. Browser Integration (optional)

Check if claude-in-chrome is available by attempting to get tab context:

mcp__claude-in-chrome__tabs_context_mcp()
✅ / ❌  Chrome connection — claude-in-chrome responds
✅ / ❌  Can create tab — tabs_create_mcp succeeds

If not available:

⬜  Chrome not connected — install claude-in-chrome extension

5. Optional Integrations

Check environment for optional integrations:

✅ / ❌ / ⬜  OpenTweet MCP — check if opentweet tools are available
✅ / ❌ / ⬜  last30days — check if ~/.claude/skills/last30days/SKILL.md exists
✅ / ❌ / ⬜  X API — check if TWITTER_API_KEY env var is set

Read the full file on GitHub · 125 lines

Changes

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.

  1. 2d ago First seen · 125 lines · 28 tokens per session scan A 12136c8dbba8

Subscribe to this mod's changes

test is a skill published in the GitHub repository Epistates/sparX (3 stars, last pushed 5mo ago), licensed MIT. It adds 28 tokens to every session and 813 once invoked, about $0.0001 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.

Related

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…

jackwener/OpenCLI · 88 tokens

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…

browser-use/browser-use · 177 tokens

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…

browser-use/browser-use · 137 tokens

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?".

jackwener/OpenCLI · 74 tokens

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.

jackwener/OpenCLI · 67 tokens

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…

jackwener/OpenCLI · 64 tokens