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 mphinance/alpha-skills --skill audio-productiongit clone --depth 1 https://github.com/mphinance/alpha-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/mphinance/alpha-skills/audio-production)<a href="https://agentmods.dev/skills/mphinance/alpha-skills/audio-production"><img src="https://agentmods.dev/badge/skills/mphinance/alpha-skills/audio-production/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/mphinance/alpha-skills/audio-production"><img src="https://agentmods.dev/badge/skills/mphinance/alpha-skills/audio-production.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.00071 | $0.01814 |
| Opus 5.5 | $0.00028 | $0.00726 |
| Sonnet 5.5 | $0.00014 | $0.00363 |
| Haiku 4.5 | $0.00007 | $0.00181 |
Grade A, and why
audio-production 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 9d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audio Production & Mastering Skill
A complete pipeline for transcribing, editing, mastering, and bundling spoken audio for Substack podcasts, YouTube replays, community calls, and dev logs.
When to Use
- Transcribing audio files (
.mp3,.wav,.m4a,.webm) into clean Markdown with timestamps and speaker labels. - Analyzing an unedited recording for dead air, mic feedback, sensitive disclosures, or rambling.
- Performing surgical cuts with smooth crossfades (
acrossfade) so transitions sound completely natural. - Mastering audio to broadcast/podcast standard (-16 LUFS, 80Hz highpass filter, adaptive noise suppression).
- Packaging deliverables: Always consolidate the cleaned audio and structured markdown transcript into a single unified directory (e.g.
clean_session/ordist/audio/).
🎙️ Transcription Engines
1. Cloud STT: OpenRouter microsoft/mai-transcribe-2
- Cost/Speed: ~$0.10/hr (half the price of Whisper Large v3 Turbo), 10x faster on long-form audio.
- Key Location:
~/projects/openrouter/.env_openrouteror$OPENROUTER_API_KEY. - Endpoint:
https://openrouter.ai/api/v1/audio/transcriptions - 25MB request cap, handled automatically. OpenRouter's own docs cap a
single transcription request at 25MB. A single
transcribe_openrouter()call over that size will fail outright -- usetranscribe_long_openrouter()for anything that might be long, which splits by measured bitrate (not a fixed duration guess, since a 32kbps voice memo and a 320kbps studio recording need very different chunk lengths to land under the same byte cap), transcribes each piece, and stitches the timestamps back onto the original file's timeline. Verified 2026-09-15 against a real 57-minute / 110MB / 257kbps file: 558 segments, zero backward-jumping timestamps across chunk boundaries, last segment's end time matched the file's true duration to five decimal places, transcribed in 64 seconds for about $0.10.
Or from the CLI:from audio_pipeline import transcribe_long_openrouter result = transcribe_long_openrouter("recording.m4a") # any length, any size # result = {"text": "...", "segments": [{"start": 0.0, "end": 7.56, "text": "..."}, ...]}python3 audio_pipeline.py -i recording.m4a --transcribe out.json. Only reach for the unwrappedtranscribe_openrouter()directly when the input is already known to be under 15MB (its internal safety margin below the 25MB cap).
What ships with it
1 file 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.
- 9d ago First seen · 145 lines · 71 tokens per session scan A 97aa22fbaff6
audio-production is a skill published in the GitHub repository mphinance/alpha-skills (28 stars, last pushed 10d ago), licensed MIT. It adds 71 tokens to every session and 1,814 once invoked, about $0.0003 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-10.
Other skills, from other repositories
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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…