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 commands/esaruoho/apple/rec-subtitlegit clone --depth 1 https://github.com/esaruoho/appleWhat 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.00073 | $0.00606 |
| Opus 5 | $0.00036 | $0.00303 |
| Sonnet 5 | $0.00015 | $0.00121 |
| Haiku 4.5 | $0.00007 | $0.00061 |
Grade A, and why
rec-subtitle 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 3d 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.
What it actually says
Run the apple-skill rec-subtitle tool on $ARGUMENTS.
Use Bash to execute (one call, then stop):
/Users/esaruoho/work/apple/bin/rec-subtitle $ARGUMENTS
/rec-subtitle <video>→ transcribes the audio →<stem>.srt. Upload the video to YouTube and add this.srtas a caption track (soft subtitles — viewers can toggle them)./rec-subtitle <video> --burn→ transcribes if needed, then hard-burns the subtitles into<stem>-subtitled.mov(white text, black outline, bottom-center; timed per cue). Use for platforms without a caption track, or when the captions must be permanent.--srt FILEuses an existing/edited.srtinstead of transcribing.--mic <stem>-mic.m4atranscribes the voice-only track (fromrec-audio split) for the cleanest transcript — best when the recording also has loud system audio.--model NAMEpicks the Whisper model (default: whisp's own default).- Proper nouns are aligned automatically.
bin/recburn-vocabulary.json(or~/.config/recburn/vocabulary.json, or.recburn-vocabulary.jsonbeside the recording) both biases Whisper (--initial_prompt) and sweeps the finished.srt, so Paketti / Renoise / Lackluster are never "Pucketty" / "Reno" / "Lacklustre". Unlisted mishearings are caught by sound (Soundex); real English words are never rewritten.--vocab FILEuses another vocabulary,--no-vocabturns it off. --fix-srt <file.srt>aligns a transcript you already have, in place (no video needed).--self-testchecks the vocabulary rules headlessly (no media, no Whisper).
Transcription runs Whisper locally via ~/work/whisp/whisp; burn-in is Apple-native
AVFoundation (video re-encoded). After the command completes, report only the lines it printed.
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.
- 3d ago First seen · 35 lines · 73 tokens per session scan A 119d314bffcf
rec-subtitle is a command published in the GitHub repository esaruoho/apple (11 stars, last pushed 6d ago), licensed MIT. It adds 73 tokens to every session and 606 once invoked, about $0.0004 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.