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.
git clone --depth 1 https://github.com/HerbertGao/ogg2mp3Wrote 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/herbertgao/ogg2mp3/convert)<a href="https://agentmods.dev/commands/herbertgao/ogg2mp3/convert"><img src="https://agentmods.dev/badge/commands/herbertgao/ogg2mp3/convert/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/herbertgao/ogg2mp3/convert"><img src="https://agentmods.dev/badge/commands/herbertgao/ogg2mp3/convert.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.00021 | $0.00356 |
| Opus 5.5 | $0.00008 | $0.00142 |
| Sonnet 5.5 | $0.00004 | $0.00071 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
convert 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.
What it actually says
用户参数：$ARGUMENTS
把第一个参数当作输入文件路径，其余作为额外 flag 透传。必须始终加上 --yes --json（slash command 是非交互上下文）。
调用形式：
ogg2mp3 convert "<file>" --yes --json [...passthrough flags]
解析 JSON 结果：
ok: true—— 转换成功。一句话告诉用户：输出路径（output）、是否带封面（cover_embedded）、嵌入了几个元数据字段（metadata_fields）cover_embedded: false—— 不是错误。主动提示用户："这个文件可能不是 QQ 音乐下载的（没有 ICNS 封面资源），MP3 已生成但无专辑封面。"- 退出码非 0 —— 转换失败。从 stderr 读
ffmpeg:开头的行抓真因，告诉用户哪一步坏了
如果用户没提供文件路径（$ARGUMENTS 为空），告诉用户用法：/ogg2mp3:convert <file>，不要瞎调命令。
如果用户没明确要求覆盖，但目标 .mp3 已存在导致 exit 1 "output exists"，问用户是否要加 --overwrite 重跑，不要自作主张覆盖。
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 · 25 lines · 21 tokens per session scan A 7060ee78fd2c
convert is a command published in the GitHub repository HerbertGao/ogg2mp3 (6 stars, last pushed 4mo ago), licensed MIT. It adds 21 tokens to every session and 356 once invoked, about $0.0001 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-08-31.
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.