Borrowing it
Nothing to install: this file belongs to bybren-llc/a-safe-pulse. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bybren-llc/a-safe-pulse/dev/.gemini/commands/media/analyze-audio.tomlgit clone --depth 1 https://github.com/bybren-llc/a-safe-pulseWrote 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/commands/bybren-llc/a-safe-pulse/analyze-audio)<a href="https://agentmods.dev/commands/bybren-llc/a-safe-pulse/analyze-audio"><img src="https://agentmods.dev/badge/commands/bybren-llc/a-safe-pulse/analyze-audio/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/commands/bybren-llc/a-safe-pulse/analyze-audio"><img src="https://agentmods.dev/badge/commands/bybren-llc/a-safe-pulse/analyze-audio.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.00000 | $0.00601 |
| Opus 5.5 | $0.00000 | $0.00240 |
| Sonnet 5.5 | $0.00000 | $0.00120 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
analyze-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 1mo 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.
This is a copy
100% identical to analyze-audio — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description = "Analyze audio content, tone, and characteristics"
prompt = """
Analyze Audio Command
Analyze audio content, tone, and characteristics using Gemini's multimodal audio capabilities.
Target: {{args}}
Supported Formats
MP3, WAV, AIFF, AAC, OGG, FLAC
Workflow
1. Detect Audio File
Verify the target audio file exists and identify its format:
!{file {{args}} 2>/dev/null || echo "File not found"}
2. Classify Audio Type
Determine the primary content type:
- Speech: Conversation, presentation, podcast, narration
- Music: Song, instrumental, soundtrack
- Ambient: Environmental sounds, sound effects, background audio
- Mixed: Combination of speech, music, and/or ambient sound
3. Analyze Characteristics
Perform detailed analysis based on content type:
For Speech:
- Language and dialect detection
- Speaking pace (words per minute estimate)
- Emotional tone (confident, nervous, enthusiastic, neutral)
- Clarity and intelligibility rating
For Music:
- Genre classification
- Tempo and rhythm description
- Instrumentation detected
- Mood and energy level
For Ambient/Mixed:
- Sound source identification
- Layering and spatial characteristics
- Dominant vs background elements
4. Generate Report
## Audio Analysis Report
### File Info
- **File**: [filename]
- **Format**: [detected format]
- **Duration**: [estimated duration]
### Content Type
[Speech / Music / Ambient / Mixed]
### Mood & Tone
[Overall mood and tonal characteristics]
### Key Segments
| Timestamp | Description | Notes |
|-----------|-------------|-------|
| 00:00:00 | [segment] | [note]|
### Technical Quality
- **Clarity**: [High / Medium / Low]
- **Background Noise**: [None / Minimal / Moderate / Heavy]
- **Dynamic Range**: [Compressed / Normal / Wide]
- **Overall Quality**: [Professional / Consumer / Low]
Output Options
--summary- Brief one-paragraph summary (default)--detailed- Full analysis report with all sections--json- Structured JSON output
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.
- 1mo ago First seen · 103 lines · 0 tokens per session scan A 98840ceb60e6
analyze-audio is a command published in the GitHub repository bybren-llc/a-safe-pulse (9 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 601 tokens. A static security scan graded it A with 0 findings. It is 100% identical to analyze-audio, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
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.
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.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.
speckit.bug.test
Validate that a previously fixed bug is resolved and record the verification report.