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/check)<a href="https://agentmods.dev/commands/indranilbanerjee/digital-marketing-pro/check"><img src="https://agentmods.dev/badge/commands/indranilbanerjee/digital-marketing-pro/check/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/check"><img src="https://agentmods.dev/badge/commands/indranilbanerjee/digital-marketing-pro/check.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.00030 | $0.00952 |
| Opus 5 | $0.00015 | $0.00476 |
| Sonnet 5 | $0.00006 | $0.00190 |
| Haiku 4.5 | $0.00003 | $0.00095 |
Grade A, and why
check 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/digital-marketing-pro:check — Pre-Publish Quality Gate
Runs the unified evaluation suite on marketing content. Wraps scripts/eval-runner.py and produces a single pass / warn / blocked decision with actionable issues.
This is the canonical pre-publish gate for any marketing content (blog posts, ad copy, emails, social posts, landing pages, press releases). An earlier version ran the same checks automatically as a global PreToolUse hook on every Write/Edit operation in every project; that hook was removed because it fired across all plugins and projects regardless of context. This command is the explicit, intentional replacement.
Quick examples
/digital-marketing-pro:check drafts/q2-launch-blog.md
/digital-marketing-pro:check drafts/healthcare-ad.md --full --brand healthfirst --evidence facts/q2-claims.json --schema ad_copy
/digital-marketing-pro:check drafts/financial-services-landing.md --compliance --brand finadvisor
/digital-marketing-pro:check "Inline content can also be checked directly."
Modes
| Flag | Mode | What it runs |
|---|---|---|
| (default) | run-quick |
hallucination + content quality + readability (~2s, no external deps) |
--full |
run-full |
All 6 dimensions including brand voice + claims + structure (when corresponding inputs provided) |
--compliance |
run-compliance |
Compliance-focused: hallucination + claims + brand voice + structure |
Optional inputs
| Flag | Purpose |
|---|---|
--brand <slug> |
Score against named brand's voice profile. Defaults to active brand if set. |
--evidence <path> |
Cross-check claims against a JSON evidence file. |
--schema <name> |
Validate structure against a named schema (blog_post, email, ad_copy, social_post, landing_page, press_release, content_brief, campaign_plan, or --schema list to see all). |
Output
The command returns a unified report with:
- Composite score (0-100) and letter grade (A+ to F)
- Per-dimension scores with weights and pass/fail status
- Issues grouped by severity (CRITICAL / WARNING)
- Each issue paired with a specific fix suggestion
- Decision: PASS (safe to publish), WARN (publish but address warnings first), or BLOCKED (CRITICAL issues must be fixed before publishing)
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 · 65 lines · 30 tokens per session scan A b16c3501f6e7
check is a command published in the GitHub repository indranilbanerjee/digital-marketing-pro (801 stars, last pushed 2d ago), licensed MIT. It adds 30 tokens to every session and 952 once invoked, about $0.0002 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.