Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add indranilbanerjee/digital-marketing-pro/plugin install 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/doctor)<a href="https://agentmods.dev/commands/indranilbanerjee/digital-marketing-pro/doctor"><img src="https://agentmods.dev/badge/commands/indranilbanerjee/digital-marketing-pro/doctor/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/doctor"><img src="https://agentmods.dev/badge/commands/indranilbanerjee/digital-marketing-pro/doctor.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.00057 | $0.00738 |
| Opus 5 | $0.00028 | $0.00369 |
| Sonnet 5 | $0.00011 | $0.00148 |
| Haiku 4.5 | $0.00006 | $0.00074 |
Grade A, and why
doctor 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 12d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/digital-marketing-pro:doctor — Per-Action Readiness Check
Resolves every action in the campaign-audit and launch-campaign skill surfaces against the currently configured connectors and reports which mode each one is in:
| Mode | What it means |
|---|---|
real |
Action runs end-to-end with no external API. Always available. |
manifest_ready |
A matching connector is configured; the action returns the exact HTTP request manifest for the orchestrator (Claude via MCP) to execute. |
stub_unconfigured |
No matching connector is configured; the action returns a structured stub plus a copy-paste setup hint. |
Quick examples
/digital-marketing-pro:doctor # full readiness map for default brand
/digital-marketing-pro:doctor --brand acme # for a named brand
/digital-marketing-pro:doctor --action inventory --channel google_ads
/digital-marketing-pro:doctor --summary # one-line counts
/digital-marketing-pro:doctor --json # machine-readable
What it does NOT do
- It does not execute write/launch actions. For that, run the action through the orchestrator (
/digital-marketing-pro:launch-campaign) which respects approval gates. - It does not make any network call. It probes
.mcp.jsonmembership and env-var presence only — credentials are never read or echoed.
Output sections
- Summary line — count of actions in each of the three modes
- Per-action table — action name, mode, operation type, configured connector or list of candidate connectors
- Unlock guide — for any stub-unconfigured action, the exact next step
- Environment block — detected surface (
claude-code-windows/claude-code-mac/claude-code-linux/cowork-sandbox) - Model curator block — registry age + severity (
ok<60d,warn60-119d,urgent>=120d), with the exactrefresh_models.pycommand when stale - Cowork+Drive routing block — only meaningful in Cowork. Shows whether
/digital-marketing-pro:cowork-setuphas been run; flagsurgentwhen Cowork is detected but routing is missing (brand state would vanish at session 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.
- 12d ago First seen · 54 lines · 57 tokens per session scan A 27fccf6317f7
doctor is a command published in the GitHub repository indranilbanerjee/digital-marketing-pro (812 stars, last pushed 4d ago), licensed MIT. It adds 57 tokens to every session and 738 once invoked, about $0.0003 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.