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/formatting)<a href="https://agentmods.dev/commands/moizibnyousaf/marketing-cli/formatting"><img src="https://agentmods.dev/badge/commands/moizibnyousaf/marketing-cli/formatting/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/formatting"><img src="https://agentmods.dev/badge/commands/moizibnyousaf/marketing-cli/formatting.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.00023 |
| Opus 5.5 | $0.00000 | $0.00009 |
| Sonnet 5.5 | $0.00000 | $0.00005 |
| Haiku 4.5 | $0.00000 | $0.00002 |
Grade A, and why
formatting 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
Run bun run stylecheck until the exit code is 0.
Don't bother with lambda-go errors.
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 · 3 lines · 0 tokens per session scan A af8e272b6fdd
formatting is a command published in the GitHub repository MoizIbnYousaf/marketing-cli (32 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 23 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
benchmark
Design and coordinate a reproducible Java performance test.
fec-tdd
Use front-end TDD workflow to implement functions, fix bugs, or refactor logic: first write failing tests, then implement minimal code, and then refactor.
test-cases
Use when writing test cases, generating tests, supplementing test coverage, or improving test completeness — auto-scans project, designs multi-dimensional test cases with coverage matrix.
bug
Reproduce then TDD-fix a ready-for-agent bug ticket in this checkout. Web bugs get a browser repro first.
verify
Run the replication-package skill's Step 6b only: the deterministic checks in scripts/verifypackage.py. Skip scaffold mode, skip the package grade, skip the FAIR block, and skip the audit report. This is the fast "does my analysis still work" pass, not a submission audit.
build
Implement the next ready task from .forge/tasks.yaml using TDD discipline.