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/evoelsewhere/evoflux/algorithmic-artnpx skills add evoelsewhere/evoflux --skill algorithmic-artgit clone --depth 1 https://github.com/evoelsewhere/evofluxWhat 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.00065 | $0.00673 |
| Opus 5 | $0.00032 | $0.00336 |
| Sonnet 5 | $0.00013 | $0.00135 |
| Haiku 4.5 | $0.00006 | $0.00067 |
Grade A, and why
algorithmic-art 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create algorithmic art
Build one self-contained browser artwork whose visual character emerges from a coherent system, not a stack of unrelated random effects. Do not load bundled templates when this skill activates.
State machine
1. FRAME
Extract the subject, intended mood, output constraints, interaction needs, and one conceptual relationship the algorithm will express. If the brief leaves an axis open, choose it deliberately instead of asking for generic preferences.
Define a compact generative system:
- entities and initial state;
- forces, rules, or mathematical relationships;
- evolution and termination behavior;
- color and composition logic;
- parameters that change the system rather than merely decorate it.
Do not imitate a living artist or reproduce a recognizable artwork. Translate references into non-exclusive attributes such as density, rhythm, geometry, palette, motion, or material quality.
2. PLAN
Choose a deterministic seed strategy and a small parameter set. State what each parameter controls and the visual range it must preserve. Prefer a few high-leverage controls over exposing every constant.
Read templates/viewer.html only now, immediately before implementation. Preserve its working shell, seed navigation, control layout, reset/regenerate actions, and download behavior; replace the artwork-specific algorithm and controls. Read templates/generator_template.js only when the planned system needs an implementation example for seeded state, animation lifecycle, or parameter wiring.
3. BUILD
Create a single HTML file with inline CSS and JavaScript. The p5.js CDN may be the only external runtime dependency. Ensure:
- identical seed and parameters produce identical initial output;
- every visible control updates the intended parameter;
- previous, next, random, jump-to-seed, reset, regenerate, and PNG download work;
- the composition remains intentional across representative seeds;
- animation stays responsive and bounds particle, history, and allocation work;
- keyboard focus, labels, reduced motion, and usable contrast are present.
What ships with it
5 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 · 80 lines · 65 tokens per session scan A 745f813a33dc
algorithmic-art is a skill published in the GitHub repository evoelsewhere/evoflux (5 stars, last pushed 5d ago), licensed Apache-2.0. It adds 65 tokens to every session and 673 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
kane-cli
Browser automation + AI test authoring via kane-cli - run browser objectives, generate & refine test scenarios/cases from a description, design requirement-linked test suites from a PRD/spec (assurance), parse NDJSON output, inspect logs, save runnable test.md. Use for any task requiring a real browser (navigate…
control-chrome
Control the user's Chrome browser for tasks that depend on existing Chrome state: tabs, logged-in sessions, or extensions. Prefer purpose-built connectors, APIs, or CLIs when available.
recent-release
Render Rove's recent releases as a self-contained, Rove-styled HTML page (Chinese by default). Reads shipped notes from packages/kobe/CHANGELOG.md + git tags, filters to user-facing changes, and emits one standalone .html file in the claude theme (terracotta on near-black, JetBrains Mono, terminal chrome). Use when…
yutori-scout
Set up continuous web monitoring with Yutori Scouts. Use when the user wants to track news, competitors, product updates, funding rounds, price changes, or any recurring web information.
plan-review-triggers
Required reading whenever drafting any multi-step proposal, implementation plan, refactor approach, or response containing file paths and decision points. Use BEFORE writing any response that lists 3+ file paths, 2+ option-tradeoffs, a "Plan:"/"Steps:"/"Concrete changes:" section, or ends with "OK to proceed?" /…
yutori-computer-use
Run local Mac desktop tasks with Yutori computer use. Use when the user wants to operate macOS apps, websites in a local browser, or cross-app workflows on the visible desktop.