rec-audio

A macOS audio post-processing command for screen recordings. It can separate the computer audio and microphone audio into independent files, or combine them into one track.

In plain words
What is it for?
Use it to prepare recordings for editing with separate system and microphone tracks, or to create a widely compatible video with one mixed audio track.
Why use it?
Video editors such as iMovie may not be able to work with multiple audio tracks embedded in one recording. Separate files let you adjust or remove each source independently.

Command

Install

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.

agentmods
npx agentmods add commands/esaruoho/apple/rec-audio
Clone the repo
git clone --depth 1 https://github.com/esaruoho/apple
Per session 65 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 343 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00065 $0.00343
Opus 5 $0.00032 $0.00171
Sonnet 5 $0.00013 $0.00069
Haiku 4.5 $0.00006 $0.00034

Measured 2d ago against content hash 19f8851fa2de, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

rec-audio 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.

commands/rec-audio.md · 25 lines

What it actually says

Run the apple-skill rec-audio tool on $ARGUMENTS.

Use Bash to execute (one call, then stop):

/Users/esaruoho/work/apple/bin/rec-audio $ARGUMENTS
  • /rec-audio split <recording.mov><stem>-system.m4a + <stem>-mic.m4a. iMovie recipe: import the .mov for the video (it carries the system audio), then drag <stem>-mic.m4a onto the timeline as a second audio track — now you can balance voice vs app sound, mute either, ripple-trim independently. iMovie can't split embedded tracks out of one file, which is why these sidecars exist.
  • /rec-audio flatten <recording.mov> [-o out.mov]<stem>-flat.mov: video (passthrough, no re-encode) + ONE mixed audio track (system+mic summed, each attenuated to 0.8 to avoid clipping). Plays both everywhere — QuickTime, iMovie, YouTube.

After the command completes, report only the lines it printed.

Changes

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.

  1. 2d ago First seen · 25 lines · 65 tokens per session scan A 19f8851fa2de

Subscribe to this mod's changes

rec-audio is a command published in the GitHub repository esaruoho/apple (11 stars, last pushed 6d ago), licensed MIT. It adds 65 tokens to every session and 343 once invoked, about $0.0003 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.