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 skills/indranilbanerjee/socialforge/setupnpx skills add indranilbanerjee/socialforge --skill setupgit 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/skills/indranilbanerjee/socialforge/setup)<a href="https://agentmods.dev/skills/indranilbanerjee/socialforge/setup"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/socialforge/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.00082 | $0.02368 |
| Opus 5 | $0.00041 | $0.01184 |
| Sonnet 5 | $0.00016 | $0.00474 |
| Haiku 4.5 | $0.00008 | $0.00237 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/socialforge:setup — API Credential Configuration
One-time setup that stores credentials persistently. Run once, works forever across all sessions.
Context efficiency
Asset-heavy skill. Grep before Read the asset catalog (${CLAUDE_PLUGIN_DATA}/socialforge/brands/<brand>/asset-index.json) — never list the asset directory. Reference generated images / videos by path, not by loading metadata. Brand profile loads once per session.
What This Does
Configures two services that SocialForge needs for creative production:
- Google Cloud Vertex AI (required for images) — Nano Banana 2 (Gemini 3.1 Flash Image) + Nano Banana Pro (Gemini 3 Pro Image)
- WaveSpeed (required for video) — Kling v3.0 Pro for image-to-video
Prerequisites
Your admin provides you with:
- A Google Cloud service account JSON file (for image generation)
- A WaveSpeed API key (for video generation)
If you are the admin, see the Admin Setup section below.
How to Run
/socialforge:setup
Interactive Flow
Step 0: Install Dependencies (Automatic)
Run this first — installs all required Python packages:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/install_deps.py"
This auto-installs: google-genai (Vertex AI), wavespeed (Kling video), Pillow (compositing), imageio-ffmpeg (video post-processing), playwright (carousels).
If any package fails, show the manual install command and continue.
Step 1: Image Generation (Vertex AI)
Check if already configured:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/credential_manager.py" status
If not configured, ask:
Image Generation Setup (Google Cloud Vertex AI)
Do you have a Google Cloud service account JSON file?
Provide the full file path (e.g., C:\Users\you\Downloads\socialforge-credentials.json)
Or type "skip" to configure later (image generation will not work).
When user provides the path:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/credential_manager.py" setup-vertex --json-path "<user-provided-path>"
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 · 265 lines · 82 tokens per session scan A 332840cfb730
setup is a skill published in the GitHub repository indranilbanerjee/socialforge (36 stars, last pushed 17d ago), licensed MIT. It adds 82 tokens to every session and 2,368 once invoked, about $0.0004 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 skills, from other repositories
ai-media-generator
為使用者產生高品質的 AI 生圖、生影片、生音樂提示詞，並在需要時透過瀏覽器自動化實際送到目標平台。涵蓋 OiiOii、Kling 3.0/O-series、Seedance 2.0/2.5、Suno v5.5、Seedream 5.0/4.0、Vidu Q3、Midjourney V8.1、Flux 1.1 Pro / Kontext、Runway Gen-4.5 / Aleph、Google Veo 3.1、Ideogram 3、Nano Banana Pro、Stable Diffusion 3.5（⚠️ OpenAI Sora 2 已於 2026-04-26 停運，API 撐到 2026-09-24，預設改推…
demo-video
Make a demo video of a piece of software: drive the app on screen while narrating what it does, generate an AI voiceover and optional on-camera presenter, and assemble everything into a finished MP4. Use when the user asks to "make a demo video", "record a demo", "create a product video", "show off this app", "make a…
demo-shorts
Cut a vertical 9:16 Short (YouTube Shorts, Instagram Reels, TikTok) from a demo video project in one of four named styles — listicle (rapid numbered beats), cohost (split screen with presenter), flashcard (typographic interstitials), or glide (immersive pan). Use when the user asks for a "short", "shorts", "vertical…
demo-script
Writing the script and shot list for a demo video, and the demo.json manifest schema. Use when planning what a product video should say and show, writing voiceover narration, structuring scenes, or editing demo.json.
demo-capture
Craft and mechanics of capturing software on screen for a demo video — rehearsing a flow, staging a window, the action-script format, pacing to narration, and macOS permissions and coordinates. Use when recording an app, driving a UI for a video, debugging a capture that looks wrong, or when clicks land in the wrong…
demo-assembly
Assembling and rendering a demo video with Remotion and ffmpeg — the timeline, transitions, captions, zoom-to-click, audio ducking, and diagnosing a render that comes out wrong. Use when rendering the final video, customising its look, or fixing timing, black frames or missing audio.