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/output-folder)<a href="https://agentmods.dev/commands/indranilbanerjee/digital-marketing-pro/output-folder"><img src="https://agentmods.dev/badge/commands/indranilbanerjee/digital-marketing-pro/output-folder/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/output-folder"><img src="https://agentmods.dev/badge/commands/indranilbanerjee/digital-marketing-pro/output-folder.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.00036 | $0.01222 |
| Opus 5 | $0.00018 | $0.00611 |
| Sonnet 5 | $0.00007 | $0.00244 |
| Haiku 4.5 | $0.00004 | $0.00122 |
Grade A, and why
output-folder 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Output Folder
Show the user where DMP actually saves the finished workflow deliverables, and (when supported) open that folder in the OS file manager. This is the answer to "where are my 50 engagement files?" — a real question from user-team feedback ("dm pro also taking too long to process" was partly about not knowing whether anything had finished saving).
Trigger
User runs /digital-marketing-pro:output-folder, or asks any variant of "where are my engagement files", "I can't find the campaign plan deliverables", "open output folder", "show me where it saved everything".
Background
DMP writes two copies of every workflow artifact:
- Internal tracking copy at
~/.claude-marketing/brands/{brand}/output/{workflow}/{run_id}/...(or$CLAUDE_PLUGIN_DATA/digital-marketing-pro/brands/{brand}/output/...when that env var is set). This is the system-of-record for/digital-marketing-pro:status, the checkpoint manager, audit history. It lives inside a dotfolder that Windows hides by default. - User-visible published copy at
~/Documents/DigitalMarketingPro/{brand}/{workflow}/{YYYY-MM}/{filename}(or wherever$DIGITAL_MARKETING_PRO_PUBLISH_DIRpoints). This is the one to surface.
The published copy was added specifically because users running the 12-Part engagement workflow couldn't find the 50-60 deliverable files it produces. They were saving — just somewhere Explorer hid by default.
Process
Step 1: Resolve the path
The published-output directory is:
$DIGITAL_MARKETING_PRO_PUBLISH_DIR/{brand}/[{workflow}/]if the env var is set, or~/Documents/DigitalMarketingPro/{brand}/[{workflow}/]otherwise.
Default to the active brand if no argument was provided. If neither is available, prompt: "Which brand's output folder? Run /digital-marketing-pro:output-folder <brand> or set up a brand with /digital-marketing-pro:brand-setup."
If the user supplied a workflow argument (e.g. engagement, campaign-plan, seo-audit), drill down to that subfolder.
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 · 112 lines · 36 tokens per session scan A 642f9bd8aaea
output-folder is a command published in the GitHub repository indranilbanerjee/digital-marketing-pro (801 stars, last pushed 2d ago), licensed MIT. It adds 36 tokens to every session and 1,222 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.