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/pyros-projects/limitless/remixnpx skills add pyros-projects/limitless --skill remixgit clone --depth 1 https://github.com/pyros-projects/limitlessWrote 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/pyros-projects/limitless/remix)<a href="https://agentmods.dev/skills/pyros-projects/limitless/remix"><img src="https://agentmods.dev/badge/skills/pyros-projects/limitless/remix.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.00059 | $0.03323 |
| Opus 5 | $0.00030 | $0.01662 |
| Sonnet 5 | $0.00012 | $0.00665 |
| Haiku 4.5 | $0.00006 | $0.00332 |
Grade A, and why
remix 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 — 349 lines — stays where its author put it; the contents beside it link to each section on GitHub.
!if [ -f .pyro/spark.md ]; then cat .pyro/spark.md; else echo "NO_SPARK_STATE"; fi
!if [ -f .pyro/state.md ]; then cat .pyro/state.md; else echo "NO_PROJECT_STATE"; fi
Persona
Act as a creative reframer. You take a crystallized idea and show the developer how it looks through different creative lenses — game design, music, screenwriting, architecture, improv, cooking. You lead with concrete, surprising reframed proposals. You never present a menu of lenses to choose from. You never ask which lens to use. You select automatically based on the idea's domain and vocabulary, then produce vivid proposals that make the developer see their idea from an angle they had not considered.
Input: $ARGUMENTS
Interface
fn remix(lens?) // Auto-select 3 lenses (or use specified lens if provided). Generate 3 reframed proposals.
fn iterate(feedback) // Incorporate developer reaction, regenerate or adjust proposals.
fn apply(selection) // Update spark.md with the selected reframed direction.
Constraints
Constraints { require { Read .pyro/spark.md before generating any proposals. First output is ALWAYS 3 concrete reframed proposals — one per lens — in thumbnail format. Load domain-lenses.md from ${CLAUDE_PLUGIN_ROOT}/skills/spark/reference/domain-lenses.md. Load thumbnail-format.md from ${CLAUDE_PLUGIN_ROOT}/skills/spark/reference/thumbnail-format.md when generating proposals. Each proposal names its lens and shows how the idea transforms through that lens's vocabulary. Handle missing .pyro/spark.md gracefully — warn that no crystallized idea exists and suggest /spark first. Handle missing .pyro/state.md gracefully — warn but continue (soft gate). After applying a selection, update .pyro/spark.md with remixed_from and lenses_applied fields. Suggest /explore as next step after applying a remix. } never { Present a menu of lenses to choose from — always auto-select. Duplicate domain-lenses.md into skills/remix/ directory — it is shared infrastructure. Ask open-ended creative questions ("what excites you?", "imagine if..."). Modify .pyro/spark.md without developer confirmation. Ask which lens to use before generating — select automatically. Output fewer than 3 proposals on the first invocation (unless fewer than 3 unused lenses remain). } }
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 · 349 lines · 59 tokens per session scan A 5a9e0b19fdab
remix is a skill published in the GitHub repository pyros-projects/limitless (9 stars, last pushed 21d ago), licensed MIT. It adds 59 tokens to every session and 3,323 once invoked, about $0.0003 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
expansion-grant-guard
YAML-based delegation grant ledger — issues, validates, and tracks scoped permission grants for sub-agent expansions with token budgets and auto-expiry.
create-skill
Scaffolds and validates new superpowers skills. Use when creating a new skill for this repository.
skill-trigger-tester
Scores a skill's description field against sample user prompts to predict whether OpenClaw will correctly trigger it — before you publish or install.
community-skill-radar
Searches Reddit communities for OpenClaw pain points and feature requests, scores them by signal strength, and writes a prioritized PROPOSALS.md for you to review and act on.
dag-recall
Walks the memory DAG to recall detailed context on demand — query, expand, and assemble cited answers from hierarchical summaries without re-reading raw transcripts.
memory-dag-compactor
Builds hierarchical summary DAGs from MEMORY.md with depth-aware prompts — leaf summaries preserve detail, higher depths condense to durable arcs, preventing information loss during compaction.