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/social-adaptgit 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/social-adapt)<a href="https://agentmods.dev/commands/indranilbanerjee/contentforge/social-adapt"><img src="https://agentmods.dev/badge/commands/indranilbanerjee/contentforge/social-adapt.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.1 | $0.00032 | $0.00466 |
| Opus 5 | $0.00016 | $0.00233 |
| Sonnet 5 | $0.00006 | $0.00093 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
social-adapt 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 5d 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:
- social-adapt — 100% identical, 0 lines differ
What it actually says
Social Adapt
This command is a thin wrapper. The complete adaptation procedure lives in
skills/cf-social-adapt/SKILL.md — read that file and
execute it end to end. Do not improvise a different flow from this wrapper.
Trigger
User runs /contentforge:social-adapt or asks to repurpose content for social media, create
social posts from an article, or promote content on social platforms.
Gather inputs
If not provided in the arguments, ask before proceeding:
- Source content — Google Drive URL, local file path, requirement ID (e.g.,
REQ-001), or pasted article text - Platforms —
all(default) or a comma-separated subset of the platforms defined inconfig/social-platform-specs.json - Optional — posts per platform (default 3, max 10), brand profile, campaign hashtag, published article URL, available image assets, tone override
Platform rules — single source of truth
Character limits, hashtag counts, and format rules come from
config/social-platform-specs.json. Read that file at run time; never use remembered
limits or any table in this wrapper.
Execute
Follow skills/cf-social-adapt/SKILL.md in full:
load source → extract shareworthy moments → apply platform specs from config →
generate posts (hook, body, CTA, hashtags, image spec, posting time) →
quality check (limit compliance, self-contained, CTA present, brand voice, no duplicates).
After adaptation
Ask: "Would you like me to:
- Generate more posts for specific platforms?
- Adapt another article?
- Create A/B variants for the top-performing hooks? (
/contentforge:cf-variants) - Translate these posts for other markets? (
/contentforge:translate)"
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.
- 5d ago First seen · 45 lines · 32 tokens per session scan A 3db06469464b
social-adapt is a command published in the GitHub repository indranilbanerjee/contentforge (26 stars, last pushed 19d ago), licensed MIT. It adds 32 tokens to every session and 466 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
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.
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?".
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.
check
Run the unified pre-publish quality gate on marketing content (hallucination + brand voice + structure + claims). Use before publishing any marketing copy.
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.
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.