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/indranilbanerjee/digital-marketing-proWrote 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/indranilbanerjee/digital-marketing-pro/status)<a href="https://agentmods.dev/commands/indranilbanerjee/digital-marketing-pro/status"><img src="https://agentmods.dev/badge/commands/indranilbanerjee/digital-marketing-pro/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/indranilbanerjee/digital-marketing-pro/status"><img src="https://agentmods.dev/badge/commands/indranilbanerjee/digital-marketing-pro/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.00023 | $0.00598 |
| Opus 5 | $0.00012 | $0.00299 |
| Sonnet 5 | $0.00005 | $0.00120 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/digital-marketing-pro:status — Unified Status Snapshot
Prints a complete status snapshot for the active Digital Marketing Pro brand. Wraps scripts/dm-status.py and surfaces health indicators that need attention.
In v3.0 and earlier, the SessionStart hook ran setup.py automatically at every Claude Code session start to print a 15-line brand summary banner across every project. v3.1 removed that hook because it fired globally regardless of context. v3.2 introduces this command as the explicit on-demand replacement, with a richer view than the old banner.
Quick examples
/digital-marketing-pro:status # Full snapshot for active brand
/digital-marketing-pro:status --brand acme-corp # Snapshot for a named brand
/digital-marketing-pro:status --quiet # One-line compact summary
/digital-marketing-pro:status --json # Machine-readable JSON
/digital-marketing-pro:status --section engagements # Only the engagements section
Sections
| Section | Contents |
|---|---|
brand |
Name, industry, voice, channels, languages, markets, competitors, primary goal |
engagements |
All engagements with current part, completed/blocked counts, days since update, pending decisions, versioned doc count |
insights |
Last 5 insights captured + days since last save + total count |
compliance |
Last 5 compliance violations + count in last 30 days |
deps |
Python version + mode (knowledge-only / lite / full) + available + missing packages |
Health indicators surfaced
After the snapshot, the skill highlights items that need attention:
- Engagements not updated in 14+ days
- Engagements with pending re-run decisions awaiting action
- Recent compliance violations (last 30 days)
- Missing Python dependencies that affect feature availability
Fast and read-only
This command never modifies state. It only reads from existing brand profile, engagement state, insights, and violations files. Safe to run at any time without side effects.
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.
- 10d ago First seen · 52 lines · 23 tokens per session scan A 67d094c90619
status is a command published in the GitHub repository indranilbanerjee/digital-marketing-pro (801 stars, last pushed 3d ago), licensed MIT. It adds 23 tokens to every session and 598 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-30.
Other commands, from other repositories
brand-setup
Configure brand voice, terminology, compliance guardrails, and style guide for content production.
output-folder
Print the absolute path to the user-visible ContentForge output folder and open it in the OS file manager.
create-content
Run the full 10-phase content production pipeline — research, draft, fact-check, humanize, and publish.
audit-content
Audit your content library for freshness decay, coverage gaps, and optimization opportunities.
content-brief
Generate a research-backed content brief with keyword data, competitor analysis, search intent, and SEO strategy.
publish
Publish finished content to Webflow or WordPress with preview, verification, and HTML export fallback.