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/socialforge/assemble-documentgit 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/assemble-document)<a href="https://agentmods.dev/commands/indranilbanerjee/socialforge/assemble-document"><img src="https://agentmods.dev/badge/commands/indranilbanerjee/socialforge/assemble-document.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.00156 |
| Opus 5 | $0.00010 | $0.00078 |
| Sonnet 5 | $0.00004 | $0.00031 |
| Haiku 4.5 | $0.00002 | $0.00016 |
Grade A, and why
assemble-document 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.
What it actually says
Assemble Document
Package all approved posts into a professional delivery document.
Process
- Load all approved posts from status-tracker.json
- Collect final images, videos, and copy from post folders
- Generate DOCX with branded formatting
- Include: post calendar view, individual post pages with visuals and copy, platform specs
- Save to FINAL/ folder
Prerequisites
- Posts must be approved (status: APPROVED_INTERNAL or higher)
- Run after /socialforge:finalize or as part of the full pipeline
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 · 20 lines · 19 tokens per session scan A 1252e695b141
assemble-document is a command published in the GitHub repository indranilbanerjee/socialforge (36 stars, last pushed 18d ago), licensed MIT. It adds 19 tokens to every session and 156 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
output-folder
Print the absolute path to the user-visible ContentForge output folder and open it in the OS file manager.
wiki-ingest
Ingest a local file into the wiki knowledge base.
create-demo-video
Record, narrate and edit a finished demo video of a piece of software.
export
Export the brain to CSV for Sheets, Looker Studio, or any BI tool.
setup
Set up PromptCut - installs deps (pip, ffmpeg), checks keys, CapCut folder.
wiki-tune
Tune wiki schema and conventions interactively.