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/aaxnpx skills add Generous-Corp/pulp --skill aaxgit 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/aax)<a href="https://agentmods.dev/skills/generous-corp/pulp/aax"><img src="https://agentmods.dev/badge/skills/generous-corp/pulp/aax.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.00044 | $0.05132 |
| Opus 5 | $0.00022 | $0.02566 |
| Sonnet 5 | $0.00009 | $0.01026 |
| Haiku 4.5 | $0.00004 | $0.00513 |
Grade A, and why
aax 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 — 405 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AAX Skill
Use this when working on Pulp's optional AAX support or when guiding users who want to build and validate AAX plugins locally.
Scope
- Supported hosts: macOS and Windows
- Unsupported: Linux and Ubuntu
- Current scope: AAX Native, including the custom editor (
AAX_CEffectGUI) and parameter gestures - Out of scope: bundling Avid assets, DSP support, PACE release automation
- Out of scope, with a caveat worth knowing: AudioSuite. The descriptor
declares
AAX_ePlugInRole_InsertOrAudioSuite, so the role is advertised, but Pulp registers noAAX_IHostProcessor— the dedicated offline-render path is not implemented. Say "the role is declared; the offline path is not implemented", not "AudioSuite works" and not "the role is absent".
The custom editor
core/format/src/aax_effect_gui.cpp embeds a Pulp editor in the Pro Tools
plugin window through the shared, format-agnostic view::PluginViewHost — the
same seam VST3 / AU v2 / AU v3 / CLAP use, so there is no AAX-specific render
path to maintain. Its ViewBridge is built from
ViewBridge::Options::hosted_editor() like every other hosted adapter — never a
hand-assembled Options, and a structural test enforces that. See the
view-bridge skill.
The editor is opt-in, and defaulting it off is deliberate — do not "fix" it.
PULP_AAX_PLUGIN registers no editor, so a plugin gets Pro Tools'
auto-generated parameter strip; PULP_AAX_PLUGIN_WITH_GUI registers the custom
editor. The strip is plain but it works, and it is the only AAX UI any Pulp
plugin has shipped with. The custom editor has not been validated in Pro Tools
itself, so a plugin that merely rebuilds must not trade a working strip for an
unproven editor — an author has to ask for it. pulp-test-aax-entry-registration
asserts both directions; if you flip the default, that suite fails, and that is
the point. Reach for PULP_AAX_PLUGIN_WITH_GUI in an example or template only
once the editor has actually been driven in Pro Tools.
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 · 405 lines · 44 tokens per session scan A f13768ae245e
aax is a skill published in the GitHub repository Generous-Corp/pulp (16 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 5,132 once invoked, about $0.0002 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…