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/godot-fun/godot-framework/audio-splitnpx skills add godot-fun/godot-framework --skill audio-splitgit clone --depth 1 https://github.com/godot-fun/godot-frameworkWhat 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.00058 | $0.00631 |
| Opus 5 | $0.00029 | $0.00316 |
| Sonnet 5 | $0.00012 | $0.00126 |
| Haiku 4.5 | $0.00006 | $0.00063 |
Grade A, and why
audio-split 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
Audio Split
Split one audio file into part 1 (start �?split point) and part 2 (split point �?end).
Rules
When this skill applies, read and follow skill-dependency-manager �?run scripts as documented, install missing tools into .dependency/.
Quick Start
Default: split at 50% of duration, output to <audio-dir>/audio-split/:
.dependency/python/python .ai/audio-split/split.py --audio path/to/audio.wav
Split at a specific time (seconds):
.dependency/python/python .ai/audio-split/split.py --audio path/to/audio.wav -s 1.25
Outputs: basename_part1.ext and basename_part2.ext.
Split Point
Provide one of:
| Flag | Meaning |
|---|---|
-s / --split-at |
Time in seconds (e.g. 1.25, 90) |
-p / --percent |
Position as percent of duration (e.g. 50 = midpoint) |
| (none) | Defaults to 50% |
If both -s and -p are given, -s wins.
Common Flags
--audio · -s / --split-at · -p / --percent · -o / --output
.dependency/python/python .ai/audio-split/split.py --audio audio/sfx.wav -s 0.4
.dependency/python/python .ai/audio-split/split.py --audio audio/sfx.wav --output path/to/out/
Originals are never modified. Supported: .wav, .mp3, .ogg, .flac, .aac, .m4a, .wma.
Agent Notes
- Use the bundled script, not hand-written
-ss/-tocommands. - Looping BGM �?splitting breaks the loop; prefer two source assets or manual crossfade planning.
- Split point at
0or at/after duration �?script errors with a clear message. - Missing Python/FFmpeg �?populate
.dependency/per skill-dependency-manager, retry same command. - FFmpeg details and manual fallback: reference.md
Tests
From repo root:
.dependency/python/python .ai/audio-split/test_split.py
Manual CLI examples: cli/audio-split.md
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.
- 3d ago First seen · 70 lines · 58 tokens per session scan A 65f87e3ebd54
audio-split is a skill published in the GitHub repository godot-fun/godot-framework (116 stars, last pushed 3d ago), licensed MIT. It adds 58 tokens to every session and 631 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…