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.
npx agentmods add commands/indranilbanerjee/contentforge/brand-setupgit clone --depth 1 https://github.com/indranilbanerjee/contentforgeWrote 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/contentforge/brand-setup)<a href="https://agentmods.dev/commands/indranilbanerjee/contentforge/brand-setup"><img src="https://agentmods.dev/badge/commands/indranilbanerjee/contentforge/brand-setup.svg" alt="Measured on agentmods" 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 | $0.00016 | $0.07209 |
| Opus 5 | $0.00008 | $0.03605 |
| Sonnet 5 | $0.00003 | $0.01442 |
| Haiku 4.5 | $0.00002 | $0.00721 |
Grade A, and why
brand-setup 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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- brand-setup — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 627 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brand Setup
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Quick Start (5 minutes)
Most users only need these 3 things to get started:
- Brand name — Your company or client name
- Voice/tone — Pick one: authoritative, conversational, technical, witty, warm, educational
- Industry — Pick one: pharma, bfsi, healthcare, legal, technology, b2b_saas, ecommerce, consumer_goods, real_estate, education
That's it. Run /contentforge:cf-style-guide and answer these 3 questions. ContentForge creates a working brand profile in under 5 minutes.
You can always add more later:
- Terminology and banned words →
/contentforge:cf-style-guide --update [brand] - Compliance guardrails → same command
- Audience personas, competitors, content pillars, visual identity → same command
- Tracking backend (Google Sheets / Airtable / Local) →
/contentforge:cf-switch-backend
Don't let setup slow you down. A minimal brand profile works. You'll get better results as you add detail over time.
Full Setup (When You're Ready for More)
Create or update a brand voice profile that the ContentForge pipeline uses for every piece of content it produces. Import from existing style guide documents, URLs, or build interactively. Captures tone, formality, personality traits, approved and banned terminology, compliance guardrails, and industry-specific requirements.
Trigger
User runs /contentforge:brand-setup or asks to set up a brand, configure brand voice, import a style guide, or onboard a new client.
Inputs
Gather the following from the user. If not provided, ask before proceeding:
-
Brand name — the name for this brand profile (used in
--brand=across all skills) -
Style guide source — one of:
- URL — public URL to a style guide page (Notion, Google Docs published link, website, Confluence)
- Document — path to a .docx or .pdf style guide file
- Manual — interactive mode where you provide voice, terminology, and guardrails step by step
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.
- 3d ago First seen · 627 lines · 16 tokens per session scan A 57bef9054431
brand-setup is a command published in the GitHub repository indranilbanerjee/contentforge (26 stars, last pushed 17d ago), licensed MIT. It adds 16 tokens to every session and 7,209 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
engagement
Run a marketing engagement using the 12-Part methodology. Subcommands: start, next, status, validate, re-run-decision, update-back, lif-show, file-tree, list-engagements, four-core, growth-plan, yearly-planner, loop.
resume
Resume a long-running DMP workflow (engagement / campaign-plan / content-engine / seo-audit / competitor-analysis / campaign-audit / launch-campaign) that was interrupted partway through.
execute-action
Actually fire a campaign-audit / launch-campaign action against its real API (vs returning a manifest). Reads credentials from env vars (no OAuth flow). Read ops auto-execute with --execute; write ops require --confirm. Logs every execution to the audit trail.
output-folder
Print + open the user-visible DMP output folder for a brand (/Documents/DigitalMarketingPro/{brand}/). Direct answer to "where did my engagement deliverables save?".
check
Run the unified pre-publish quality gate on marketing content (hallucination + brand voice + structure + claims). Use before publishing any marketing copy.
doctor
Per-action readiness diagnostic. Shows which campaign-audit and launch-campaign actions are live (manifest-ready) vs blocked (stub-unconfigured) in the current environment, with one-step setup hints for the blocked ones. Now includes model-registry freshness + Cowork+Drive routing status.