Borrowing it
Nothing to install: this file belongs to IvanWng97/pixtuoid. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/IvanWng97/pixtuoid/main/.claude/skills/procedural-lofi/SKILL.mdgit clone --depth 1 https://github.com/IvanWng97/pixtuoidWrote 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/ivanwng97/pixtuoid/procedural-lofi)<a href="https://agentmods.dev/skills/ivanwng97/pixtuoid/procedural-lofi"><img src="https://agentmods.dev/badge/skills/ivanwng97/pixtuoid/procedural-lofi/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/ivanwng97/pixtuoid/procedural-lofi"><img src="https://agentmods.dev/badge/skills/ivanwng97/pixtuoid/procedural-lofi.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00142 | $0.03516 |
| Opus 5.5 | $0.00057 | $0.01406 |
| Sonnet 5.5 | $0.00028 | $0.00703 |
| Haiku 4.5 | $0.00014 | $0.00352 |
Grade A, and why
procedural-lofi 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 15d 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.
(`yt-dlp` / `curl` for analysis only; for an endless live stream, `yt-dlp -g` gets the How it starts
The opening of the file, as written. The whole thing — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Procedural Lofi — build a soundtrack in code, not in a sample pack
This skill is the end-to-end recipe for a lofi bed (and its sibling ambient sounds: rain, keystrokes, door chimes, printer, water cooler…) that is synthesized at runtime from constants — zero audio files, zero royalties, and no two minutes ever sound the same.
Two documents ship alongside this one:
reference/LOFI-BIBLE.md— the parameter tables. Harmony (chord grammar, voice-leading, register clamps), groove (swing %, drag ms, velocity curves), per-voice sound design (pad / bass / EP keys / sparkle / drums / texture / tape chain), mix targets (band shares, HPF strategy, loudness), and generative lessons from prior art. Every number is cited and, where it conflicts with a measurement, the measurement wins.scripts/— the Python (numpy) pipeline:analyze_*.py(fingerprint a reference),synth_audition.py(a runnable numpy synth that produces.wavauditions), andexport_score.py(freeze a good take into a constants table for the port).
Read those two when you reach the step that needs them. This file is the map.
The core idea (why code, not samples)
A sampled lofi loop is: (a) a licensing liability, (b) heavy to bundle, and (c) audibly repetitive — the human brain catches a loop seam on the 3rd or 4th pass. Synthesizing it solves all three:
- Legal: acoustic parameters are not copyrightable. You measure a reference to get target numbers (this band has 55% of the power, the centroid sits at 150 Hz, drops land 13 dB above the bed). You never keep or ship the reference bytes. What ships is your own oscillator code hitting those numbers.
- Size: a few kilobytes of constant tables + a synth function vs. megabytes of PCM.
- Never repeats (in practice), from three stacked tricks: (1) the frozen musical composition — pad, drums, and the melody (keys + sparkle) — loops in lockstep, but the loop is made long enough that its repetition doesn't fatigue (this project doubled its day loop from 4 to 8 bars precisely because a short looped melody was audibly repetitive — "loop the bed" does not mean "make it short"); (2) the genuinely-stochastic layers — rain drops and keystrokes — are scattered fresh at runtime from a seeded RNG, laid over the loop; (3) a busy-ness stem mixer fades whole stems (drums, keys…) in and out by how active the scene is, so the arrangement keeps changing even though the notes don't. The result reads as "never the same two minutes" without regenerating harmony. (Regenerating melody live is possible but it's the hard, optional part — the shipped product froze the melody and leaned on 1–3 instead.)
What ships with it
7 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.
- 15d ago Changed aab93723cc60
- 26d ago Changed · -6 lines 88ff3bc6debb
- 1mo ago First seen · 225 lines · 142 tokens per session scan A 96b7a62af6ad
procedural-lofi is a skill published in the GitHub repository IvanWng97/pixtuoid (491 stars, last pushed 15d ago), licensed MIT. It adds 142 tokens to every session and 3,516 once invoked, about $0.0006 per session on Opus 5.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-30.
Other skills, from other repositories
ast-grep
Use for ast-grep project setup, rule authoring, rule debugging, and structural search workflows.
skill-installer
Install VT Code skills into /.agents/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo, including private repos.
cmd-review
Review the current diff or selected files (usage: /review [instructions | --last-diff | --target | --file | files...] [--style ]).
vtcode-companion
Delegate repository investigation, coding plans, explicitly requested implementation, and verification review to a connected local VT Code Companion MCP service.
unifly
Inspect and manage UniFi Network infrastructure with the unifly CLI: devices, clients, VLANs, WiFi, firewall, VPN, switch ports, site settings, and cloud fleets. Use for UniFi network configuration, monitoring, and troubleshooting, not UniFi Protect camera or recording management.
unifly
Inspect and manage UniFi Network infrastructure with the unifly CLI: devices, clients, VLANs, WiFi, firewall, VPN, switch ports, site settings, and cloud fleets. Use for UniFi network configuration, monitoring, and troubleshooting, not UniFi Protect camera or recording management.