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 commands/timmx7/styx/setupgit clone --depth 1 https://github.com/timmx7/styxWhat 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.00011 | $0.00283 |
| Opus 5 | $0.00005 | $0.00142 |
| Sonnet 5 | $0.00002 | $0.00057 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
setup scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://localhost:8080/health | jq . What it actually says
/styx:setup
Help the user set up and start the Styx AI API gateway.
Steps
- Check if Docker and Docker Compose are installed. If not, inform the user.
- Check if Styx is already cloned locally. Look for a
styxdirectory or adocker-compose.ymlwith styx references. - If not present, clone the repo:
git clone https://github.com/styx-hq/styx.git cd styx - Run the setup wizard:
./setup.sh - Start the services:
docker compose up -d - Verify health:
curl -s http://localhost:8080/health | jq . - Report the status to the user:
- Gateway URL: http://localhost:8080
- Dashboard URL: http://localhost:3000
- MCP endpoint: http://localhost:8080/mcp
If the user passes --skip-auth, remind them to set SKIP_AUTH=true in the environment for development mode.
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 · 38 lines · 11 tokens per session scan A 385b28ef14d2
setup is a command published in the GitHub repository timmx7/styx (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 283 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.