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/content-briefgit 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/content-brief)<a href="https://agentmods.dev/commands/indranilbanerjee/contentforge/content-brief"><img src="https://agentmods.dev/badge/commands/indranilbanerjee/contentforge/content-brief.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.00019 | $0.00443 |
| Opus 5 | $0.00010 | $0.00221 |
| Sonnet 5 | $0.00004 | $0.00089 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
content-brief 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 4d 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:
- content-brief — 100% identical, 0 lines differ
What it actually says
Content Brief
This command is a thin wrapper. The complete brief-generation procedure lives in
skills/cf-brief/SKILL.md — read that file and execute it
end to end. Do not improvise a different flow from this wrapper.
Trigger
User runs /contentforge:content-brief or asks to create a brief, plan content, research a
topic for writing, or prepare a content outline.
Gather inputs
If not provided in the arguments, ask before proceeding:
- Keyword or topic — the primary keyword or topic to build the brief around
- Target audience — who this content is for (e.g., "Healthcare CIOs", "Small business owners")
- Optional — content type preference (article, blog, whitepaper, FAQ, video script), 1-5 competitor URLs, SEO goal (
traffic|conversions|awareness), brand profile name
Execute
Follow skills/cf-brief/SKILL.md in full:
keyword research → competitor & E-E-A-T analysis → search intent classification →
audience pain points & questions → recommended outline → SEO strategy →
AEO/GEO strategy (AI Overview presence, citation-worthiness, answer blocks) →
success metrics (quality score goal 8.5+).
If SEO connectors (Ahrefs, Similarweb) are not connected, use the skill's web-search
fallback and label estimates as estimates. To connect: /contentforge:cf-connect ahrefs.
After the brief
Ask: "Would you like me to:
- Start content production using this brief? (
/contentforge:create-content) - Create briefs for related topics?
- Adjust the brief for a different audience or content type?
- Check if this topic overlaps with existing content? (
/contentforge:audit-content) - Plan a content calendar around this topic cluster? (
/contentforge:cf-calendar)"
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.
- 4d ago First seen · 44 lines · 19 tokens per session scan A 3e2020450b6b
content-brief is a command published in the GitHub repository indranilbanerjee/contentforge (26 stars, last pushed 17d ago), licensed MIT. It adds 19 tokens to every session and 443 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.