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/socialforgeWrote 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/socialforge/brand-setup)<a href="https://agentmods.dev/commands/indranilbanerjee/socialforge/brand-setup"><img src="https://agentmods.dev/badge/commands/indranilbanerjee/socialforge/brand-setup/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/socialforge/brand-setup"><img src="https://agentmods.dev/badge/commands/indranilbanerjee/socialforge/brand-setup.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.00025 | $0.00238 |
| Opus 5.5 | $0.00010 | $0.00095 |
| Sonnet 5.5 | $0.00005 | $0.00048 |
| Haiku 4.5 | $0.00003 | $0.00024 |
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 12d 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.
What it actually says
Brand Setup
Create or update a brand profile for SocialForge production.
Process
- Check API credentials are configured (run /socialforge:setup first if not)
- Ask for brand name, industry, colors, platforms, asset source
- Create brand config files in the workspace
- Optionally add logo, fonts, visual style, compliance rules, approval chain, hashtags
- Validate brand profile completeness
First Time
Run with a brand name to create a new profile:
/socialforge:brand-setup MyBrand
Update Existing
Add --update to modify an existing brand:
/socialforge:brand-setup MyBrand --update
Switch Active Brand
/socialforge:brand-setup OtherBrand --switch
Or use the dedicated command: /socialforge:switch-brand OtherBrand
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.
- 12d ago Changed · +1 lines · +5 tokens per session e74708c50911
- 1mo ago First seen · 34 lines · 20 tokens per session scan A 526b2050f017
brand-setup is a command published in the GitHub repository indranilbanerjee/socialforge (42 stars, last pushed 9d ago), licensed MIT. It adds 25 tokens to every session and 238 once invoked, about $0.0001 per session on Opus 5.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
design-to-code
Mockup-to-component pipeline using Google Stitch, 21st.dev, and Storybook MCP. Accepts a screenshot, a description, or a URL and produces production-ready React components, checking existing Storybook components before generating anything new. Use when implementing UI from a mockup or screenshot. To call the MCP tool…
design-context-extract
Extract design DNA from app screenshots, live URLs, or screen recordings using Google Stitch — color palettes, typography, spacing tokens, component patterns, and motion specs as design-tokens.json or Tailwind config. Use when the user points to a screenshot, URL, or video and asks to extract or audit the design…
design-import
Scaffolds React components from a Claude Design handoff bundle and stops at files on disk: no stories, no tests, no pull request. Use when handed a claude.ai/design URL or a local bundle file; when that same scaffold should carry on through test generation, browser verification and an opened PR, run /ork:design-ship…
design-ship
One-shot pipeline turning a claude.ai/design link into a pull request: scaffold via /ork:design-import, stories and specs via /ork:cover, browser verification via /ork:expect, then open the PR. Use when a design link should come back as a PR with no intermediate steps; if all you need is the components written to…
create-short
Create a short-form vertical video (TikTok, Instagram Reels, YouTube Shorts). Optimized 9:16 pipeline with auto-captions, hook-first structure, and background music mood selection.
create-video
Full video production pipeline — from a text prompt to a rendered MP4 with voiceover, music, sound effects, stock footage, and motion graphics. The flagship command of Remotion Superpowers.