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 skills add JoseArron/skills --skill create-procedural-artgit clone --depth 1 https://github.com/JoseArron/skillsWrote 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/josearron/skills/create-procedural-art)<a href="https://agentmods.dev/skills/josearron/skills/create-procedural-art"><img src="https://agentmods.dev/badge/skills/josearron/skills/create-procedural-art/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/josearron/skills/create-procedural-art"><img src="https://agentmods.dev/badge/skills/josearron/skills/create-procedural-art.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00055 | $0.00560 |
| Opus 5.5 | $0.00022 | $0.00224 |
| Sonnet 5.5 | $0.00011 | $0.00112 |
| Haiku 4.5 | $0.00006 | $0.00056 |
Grade A, and why
create-procedural-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 7d 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create procedural art
Translate direction into a controllable visual system. The code is the medium; its output still needs art review.
Choose the rendering path
Read the art contract, target device, stack, and proof renders. Follow constraints such as code-only geometry, a shared rig, or a specific engine. Choose SVG, Canvas, shaders, mesh geometry, or an established library based on behavior and export.
Choose subject, visual grammar, and production constraints from the brief. Abstract graphics, lettering, environments, and representational subjects need different parameters and proofs.
Extending the established vector system can be enough for a static graphic. A bitmap texture belongs with image generation when requested and allowed. Do not hide raster images in a deliverable described as entirely procedural.
Build the visual grammar
Expose parameters representing art decisions: proportions, silhouette landmarks, contour variation, palette, material response, texture scale, light, camera, composition, and motion inputs. Separate shape, rendering, and behavior only where it makes requested variation easier.
- Seed randomness when reproduction matters. Keep identity stable while changing rendering or motion.
- For recognizable subjects, preserve defining landmarks at intended size. For abstract work, check the requested composition, relationships, and variation.
- For 3D, check silhouette before material polish, then light, roughness, depth, occlusion, and camera. For 2D, check contour, values, layering, and texture scale.
- When the direction calls for irregularity or texture, make it deliberate. Choose clean geometry or variation according to the brief.
- Use the same source geometry or composition across render comparisons when the question is the renderer. Changing the subject confounds the comparison.
Prove the hard part
Build a representative still, animation, or interactive study exposing the difficult requirement. For exploration, compare different treatments at the same scale and view. For a selected direction, refine its traits instead of continuing to branch.
What ships with it
2 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.
- 7d ago Changed a15b20a0f7a2
- 8d ago First seen · 37 lines · 55 tokens per session scan A 791e4f81a140
create-procedural-art is a skill published in the GitHub repository JoseArron/skills (2 stars, last pushed 8d ago), licensed MIT. It adds 55 tokens to every session and 560 once invoked, about $0.0002 per session on Opus 5.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-10-11.
Other skills, from other repositories
playtest-report
Structured playtest report template, or turn existing playtest notes into structured feedback.
godot-signals-groups
Build event-driven, decoupled Godot 4.7 gameplay with signals and node groups: declare and emit custom signals, connect with Callables (incl. bind/one-shot), and broadcast to many nodes via groups and callgroup. Use when wiring node communication in a Godot project, replacing tight references with signals…
motion
Reconstruct a skeleton from calibrated mesh projections and sequential VLM joint annotations, then fit joints and skin weights. Generate motion from joint-position trajectories, rhythm and contact constraints through IK; refine bone orientation against the action, then export, retarget and validate on the target mesh.
unity-addressables
Manage Addressables groups, entries, profiles and content builds (com.unity.addressables, reflection-based).
threejs-exposure-color-grading
Build a measured exposure and grading path in Three.js. Use for a 64x36 encoded luminance meter, asynchronous readback, weighted log-average exposure, asymmetric adaptation, single tone-map ownership, and a generated 32-cube post-tone-map LUT.
unity-manual-component
Manually add, configure, reorder, and copy components on GameObjects using Unity Editor UI. For one-off Inspector workflows that do not need REST automation.