finalize

A command that closes a month’s content cycle and packages approved material into delivery folders.

In plain words
What is it for?
Preparing a finished monthly social-media content package for delivery, with an option to include unapproved posts or upload to Drive when a Drive connection is enabled.
Why use it?
It removes the need to gather approved posts and organize the delivery files by hand. It also checks that required approvals, the calendar, and compliance checks are complete.

Command

Part of the socialforge plugin — 20 skills, 25 commands, 5 agents shipped together

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/finalize
Clone the repo
git clone --depth 1 https://github.com/indranilbanerjee/socialforge

Or install socialforge, the plugin that ships this one along with the rest of its 20 skills, 25 commands, 5 agents.

Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 112 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.00010 $0.00112
Opus 5 $0.00005 $0.00056
Sonnet 5 $0.00002 $0.00022
Haiku 4.5 $0.00001 $0.00011

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

Security

Grade A, and why

finalize 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 3d 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/finalize.md · 17 lines

What it actually says

Finalize

Package all approved content into the delivery folder structure. Runs /socialforge:finalize-month skill.

Pre-Check

  • All posts must be FINAL status (or --force to include unapproved)
  • Calendar document must be assembled
  • All compliance checks passed

Output

Organized FINAL/ folder on disk; optional Drive upload only if a Drive MCP has been opted into.

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. 3d ago First seen · 17 lines · 10 tokens per session scan A 4c21f04ed1b0

Subscribe to this mod's changes

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