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 instructions/noizefield/audio-plugin-coder/agents-mdgit clone --depth 1 https://github.com/Noizefield/audio-plugin-coderWhat 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.01128 | $0.01128 |
| Opus 5 | $0.00564 | $0.00564 |
| Sonnet 5 | $0.00226 | $0.00226 |
| Haiku 4.5 | $0.00113 | $0.00113 |
Grade A, and why
audio-plugin-coder AGENTS.md 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audio Plugin Coder — Agent Guidance
Scope
These instructions apply to the entire repository and are written for any coding agent that reads the AGENTS.md standard (Codex, Cursor, and others). Agents with their own APC configuration (Claude Code via .claude/, Kilo via .kilocode/) should treat that configuration as primary; this file stays consistent with it.
First run
- New checkouts should start with
/apc-setup(skill actionsetup) before creating plugins. - Setup writes machine-local
apc.config.json(seeapc.config.example.json). Paths, UI defaults, and per-phase model preferences live there. - Resolve plugin/build/release directories via
scripts/lib/Get-ApcPaths.ps1orscripts/lib/apc-paths.sh— do not assume./pluginsif config overrides exist. /apc-shipwrites installers and zips topaths.release_dir(defaultrelease/). Do not usedist/as the ship output.
Attribution
- Do not add
Co-authored-bytrailers for AI agents. - Do not list AI agents as contributors, authors, or acknowledgments.
- Do not post GitHub comments, reviews, or issues in the name of an AI agent.
- If a host injects an AI co-author trailer into a commit message, strip it before the commit is pushed.
APC Workflow
- Use the
audio-plugin-coderskill for APC lifecycle work. - Primary slash commands are prefixed:
/apc-setup,/apc-dream,/apc-plan,/apc-design,/apc-impl,/apc-test,/apc-debug,/apc-ship,/apc-status,/apc-resume,/apc-new. - Short forms (
/dream,/design,/impl, …) remain as deprecated aliases that redirect to/apc-*. - If the agent host does not expose slash commands, use the
audio-plugin-coderskill or an equivalent natural-language request.
Codex
- Invoke APC as
$audio-plugin-coder:audio-plugin-coder <action> <PluginName>or use an equivalent natural-language request. - Actions include
setup,dream,plan,design,impl,test,debug,status,resume,ship,new(also acceptapc-dreamstyle names by stripping theapc-prefix). - Never use Codex
/planor/statusas APC workflow commands; those names are reserved by Codex built-ins. Prefer/apc-plan//apc-statusin docs, or the skill actions above. - See
docs/codex-compatibility.mdfor setup and the full command mapping.
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 · 68 lines · 1,128 tokens per session scan A 0ccbf1db0167
audio-plugin-coder AGENTS.md is an instructions file published in the GitHub repository Noizefield/audio-plugin-coder (313 stars, last pushed 7d ago), licensed MIT. It adds 1,128 tokens to every session, about $0.0056 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-30.
Other instructions, from other repositories
Paperlab AGENTS.md
Instructions for NourMtir0722/Paperlab, covering paperlab — for coding agents, integrating paperlab into a project, stage mode — paper as architecture, content types and lighting is data, not an enum.
markdy-com copilot-instructions.md
Instructions for HoangYell/markdy-com, a project described as: 🎬 Open-source animated architecture diagrams as code. Diagram-native DSL, 17 layout engines, Web Animations API, and MCP server for AI agents.
diffusers AGENTS.md
Instructions for huggingface/diffusers, a project described as: 🤗 Diffusers: State-of-the-art diffusion models for image, video, and audio generation in PyTorch.
comfy-prompt-studio AGENTS.md
Instructions for yxhpy/comfy-prompt-studio, covering agents.md - ai 代理配置文档, ai 提供商, 1. ollama (默认), 2. gemini and 提示词生成服务.
davinci-resolve-mcp AGENTS.md
Instructions for apvlv/davinci-resolve-mcp, covering project knowledge base, structure, where to look, code map and conventions.
lianhuanhua-skills AGENTS.md
Instructions for littlewindy123/lianhuanhua-skills, covering agents.md, project goal, architecture rules, commands and before committing.