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/MoizIbnYousaf/marketing-cliWrote 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/moizibnyousaf/marketing-cli/upgrade-mediabunny)<a href="https://agentmods.dev/commands/moizibnyousaf/marketing-cli/upgrade-mediabunny"><img src="https://agentmods.dev/badge/commands/moizibnyousaf/marketing-cli/upgrade-mediabunny/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/moizibnyousaf/marketing-cli/upgrade-mediabunny"><img src="https://agentmods.dev/badge/commands/moizibnyousaf/marketing-cli/upgrade-mediabunny.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.00228 |
| Opus 5 | $0.00000 | $0.00114 |
| Sonnet 5 | $0.00000 | $0.00046 |
| Haiku 4.5 | $0.00000 | $0.00023 |
Grade A, and why
upgrade-mediabunny 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 6d 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
- Find the latest version of Mediabunny:
npm view mediabunny version - Look in the root package.json and update the version of Mediabunny to that version in the
catalogsection. - Also upgrade @mediabunny/mp3-encoder and @mediabunny/ac3 to the same version in the
catalogsection. - Look in packages/template-*/package.json and update the version of Mediabunny (and @mediabunny/* packages if present) to the same version. Templates use explicit versions (not
catalog:), so they must be updated manually. - Update
packages/cli/src/extra-packages.tswith the new Mediabunny version. - Update
packages/studio-shared/src/package-info.tswith the new Mediabunny version inextraPackages. - Update
packages/docs/docs/mediabunny/version.mdxcompatiblity table. To find the next version this upgrade is going to be applied, look in the root package.json for the version and increment the patch version by one - Run
bun iin the end.
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.
- 6d ago First seen · 9 lines · 0 tokens per session scan A a8590aa312a4
upgrade-mediabunny is a command published in the GitHub repository MoizIbnYousaf/marketing-cli (31 stars, last pushed 23d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 228 tokens. 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-09-03.
Other commands, from other repositories
community-harvest
Mine community channels (Discord, Slack, Telegram) for recurring questions, pain points, and feature requests. Produces actionable content briefs and documentation gap reports.
lesson-capture
Record structured lessons after significant tasks. Builds a persistent knowledge base that improves future agent performance. Run with an optional summary or use review to read past lessons.
security-audit
Full security scan of the workspace. Checks for credential leaks, file permissions, gitignore coverage, and hardcoded secrets.
blog-draft
Write a 1,200-2,000 word blog article as plain semantic HTML from an approved outline. Second step in the blog production pipeline.
reference-capture
Capture a reference screenshot of the live site or an existing asset before building something new. Enforces SOUL principle.
post-today
Post today's approved content to X, auto-reply with {{WEBSITEURL}} link, and stage crosspost drafts.