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/generous-corp/pulp/faustnpx skills add Generous-Corp/pulp --skill faustgit clone --depth 1 https://github.com/Generous-Corp/pulpWrote 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/generous-corp/pulp/faust)<a href="https://agentmods.dev/skills/generous-corp/pulp/faust"><img src="https://agentmods.dev/badge/skills/generous-corp/pulp/faust.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.00029 | $0.01513 |
| Opus 5 | $0.00015 | $0.00757 |
| Sonnet 5 | $0.00006 | $0.00303 |
| Haiku 4.5 | $0.00003 | $0.00151 |
Grade A, and why
faust 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 today.
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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FAUST DSL
Use this skill when a task involves writing, generating, or testing FAUST-based processors in Pulp.
Truthful Position
Pulp supports FAUST as an offline codegen DSL. The FAUST compiler is an optional external tool; pre-generated C++ is checked into the source tree so builds work without a FAUST installation.
Supported now:
.dspsource files with offline codegen to C++ headersFaustProcessor<T>template that bridges any FAUST-generateddspsubclass into Pulp'sProcessormodel- automatic parameter reflection from FAUST
buildUserInterface()intoStateStore - bus layout detection from
getNumInputs()/getNumOutputs() - metadata extraction (
name,author,version) intoPluginDescriptor - CMake integration via
PulpFaust.cmake(pulp_faust_generate,pulp_add_faust_test) - three working examples: gain, filter, tremolo
Not supported by this skill:
- FAUST MIDI mapping
- FAUST polyphony /
declare options "[midi:on][nvoices:N]" - runtime JIT compilation
@gfx/ FAUST GUI — FaustProcessor reportshas_editor() = false- soundfile support
Core Files
| File | Purpose |
|---|---|
core/dsl/include/pulp/dsl/faust_base.hpp |
Self-contained FAUST base classes (dsp, UI, Meta) |
core/dsl/include/pulp/dsl/faust_processor.hpp |
FaustProcessor<T> template and PulpFaustUI |
core/dsl/include/pulp/dsl/dsl_processor.hpp |
DslProcessor base class shared across DSL lanes |
tools/cmake/PulpFaust.cmake |
CMake module: pulp_faust_generate(), pulp_add_faust_test() |
examples/faust-gain/ |
Stereo gain — simplest FAUST example |
examples/faust-filter/ |
Parametric filter example |
examples/faust-tremolo/ |
Tremolo with rate/depth |
How It Works
FAUST offline codegen produces a C++ class derived from ::dsp. Pulp provides self-contained base classes in faust_base.hpp so the generated code compiles without the FAUST architecture headers. FaustProcessor<T> wraps the generated class:
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.
- today First seen · 166 lines · 29 tokens per session scan A 357b597c0582
faust is a skill published in the GitHub repository Generous-Corp/pulp (16 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 1,513 once invoked, about $0.0001 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-09-04.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…