setup

A one-time command for setting up the credentials needed to generate social media images and videos through external services.

In plain words
What is it for?
Use it to connect Google Cloud for image generation, WaveSpeed for video generation, or check which services are already configured.
Why use it?
It checks whether the required access is configured, validates the credentials, and stores them for later use.

Command

Install

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.

agentmods
npx agentmods add commands/indranilbanerjee/socialforge/setup
Clone the repo
git clone --depth 1 https://github.com/indranilbanerjee/socialforge
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 167 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00013 $0.00167
Opus 5 $0.00006 $0.00084
Sonnet 5 $0.00003 $0.00033
Haiku 4.5 $0.00001 $0.00017

Measured 2d ago against content hash 1dcd7de29453, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

commands/setup.md · 25 lines

What it actually says

Setup

One-time configuration for SocialForge API credentials.

Process

  1. Check current credential status
  2. If image generation not configured: prompt for Google Cloud service account JSON path
  3. If video generation not configured: prompt for WaveSpeed API key
  4. Validate and store credentials persistently
  5. Show summary of configured services

What You Need

Get from your admin:

  • Google Cloud JSON file (for image generation via Vertex AI)
  • WaveSpeed API key (for video generation via Kling v3.0)

Quick Check

/socialforge:setup --status shows what is currently configured without changing anything.

Changes

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.

  1. 2d ago First seen · 25 lines · 13 tokens per session scan A 1dcd7de29453

Subscribe to this mod's changes

setup is a command published in the GitHub repository indranilbanerjee/socialforge (36 stars, last pushed 15d ago), licensed MIT. It adds 13 tokens to every session and 167 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.