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/stepolan/marketing-repo-templateWrote 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/stepolan/marketing-repo-template/content-status)<a href="https://agentmods.dev/commands/stepolan/marketing-repo-template/content-status"><img src="https://agentmods.dev/badge/commands/stepolan/marketing-repo-template/content-status/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/stepolan/marketing-repo-template/content-status"><img src="https://agentmods.dev/badge/commands/stepolan/marketing-repo-template/content-status.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.00015 | $0.00361 |
| Opus 5 | $0.00008 | $0.00180 |
| Sonnet 5 | $0.00003 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
content-status 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 9d 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
Scan all content directories and report the current status.
-
Scan these directories:
corporate/drafts/blog/— blog post draftsauthors/*/drafts/linkedin/— LinkedIn drafts (per author)authors/*/posted/linkedin/— published LinkedIn posts (per author)authors/*/ideas/— idea backlog (per author)corporate/ideas/— corporate ideascampaigns/— active campaignswebsite/knowledge-base/— AEO articles
-
For each file found, report:
- Filename
- Status (draft, published, idea)
- Campaign tag (if present in frontmatter)
- Last modified date
-
Cross-reference with
strategy/content-calendar.md:- Flag any scheduled content that does not have a draft file
- Flag any draft files not tracked in the calendar
-
Output a summary table:
## Content Status Report ### Blog Posts | File | Status | Campaign | Last Modified | |------|--------|----------|---------------| ### LinkedIn | File | Status | Campaign | Last Modified | |------|--------|----------|---------------| ### Campaigns | Campaign | Pieces | Status | |----------|--------|--------| ### Gaps - [List any scheduled content without drafts] - [List any drafts not in the calendar]
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.
- 9d ago First seen · 49 lines · 15 tokens per session scan A 5964ddce4c77
content-status is a command published in the GitHub repository stepolan/marketing-repo-template (2 stars, last pushed 4mo ago), licensed MIT. It adds 15 tokens to every session and 361 once invoked, about $0.0001 per session on Opus 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
repurpose
Fan a QA'd long-form piece (blog, research, weekly report) down into 6 channel-native formats — X thread, X singles, LinkedIn article, newsletter snippet, and pull-quote cards. Every output is canon-checked and staged for review.
blog-assets
Build HTML templates for each visual placeholder in a blog article and batch-export them as 1200x675 PNGs at 2x. Fourth step in the blog production pipeline.
blog-pipeline
Reference document showing the full Blog Engine flow with human approval gates. This is not an executable command — it's a map of how blog commands connect.
compliance-check
Jurisdiction-aware content compliance validation. Scans copy for regulatory violations, banned claims, missing disclaimers, and financial promotion language.
blog-publish
Push a completed blog article to the CMS -- upload images, create CMS item, sync components. Final step in the blog production pipeline.
community-harvest
Mine community channels (Discord, Slack, Telegram) for recurring questions, pain points, and feature requests. Produces actionable content briefs and documentation gap reports.