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/moizibnyousaf/marketing-cli/add-buggit 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/add-bug)<a href="https://agentmods.dev/commands/moizibnyousaf/marketing-cli/add-bug"><img src="https://agentmods.dev/badge/commands/moizibnyousaf/marketing-cli/add-bug.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00150 |
| Opus 5 | $0.00000 | $0.00075 |
| Sonnet 5 | $0.00000 | $0.00030 |
| Haiku 4.5 | $0.00000 | $0.00015 |
Grade A, and why
add-bug 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 today.
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
Add a new bug entry to packages/bugs/api/[v].ts.
The user will describe the bug and the affected version(s). Add the new entry at the top of the bugs array (after the opening bracket), following the existing format:
{
title: '<short title>',
description: '<description with upgrade instruction>',
link: 'https://remotion.dev/changelog',
versions: ['<affected versions>'],
},
Rules:
- The description should tell users which version to upgrade to.
- The link should be
https://remotion.dev/changelogunless the user provides a specific link. - Add the entry at the top of the array so the most recent bugs come first.
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.
- today First seen · 19 lines · 0 tokens per session scan A 8703eadbbb5d
add-bug is a command published in the GitHub repository MoizIbnYousaf/marketing-cli (31 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 150 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.
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.
help
Print all available commands grouped by use case. When the user runs /help, output the full index below.
reference-capture
Capture a reference screenshot of the live site or an existing asset before building something new. Enforces SOUL principle.
start
Walks a first-time user through EVC setup. Checks if the system is configured, offers industry starter, collects required vars, runs setup, and runs a demo command.