fb-ads-automation: Command for Claude Code

.claude/commands/fb-ads/new-campaign.md

new-campaign is a command for Claude Code from shashankrai1983/fb-ads-automation. It costs 0 tokens per session (2,370 once invoked), scanned A, original, MIT.

An interactive wizard for creating a new Facebook advertising campaign from scratch. It loads client, brand, business, performance, and budget context before asking for campaign details.

In plain words
What is it for?
Use it to choose a client, review current performance and guidelines, set up campaign components, and prepare a new campaign without making it live automatically.
Why use it?
It helps create campaigns using the right account and existing business information while keeping every new advertising item paused until approval.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is shashankrai1983/fb-ads-automation's own configuration. It tells Claude Code how to work on fb-ads-automation itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything fb-ads-automation configures →

Reuse

Borrowing it

Nothing to install: this file belongs to shashankrai1983/fb-ads-automation. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/shashankrai1983/fb-ads-automation/main/.claude/commands/fb-ads/new-campaign.md
Clone the repo
git clone --depth 1 https://github.com/shashankrai1983/fb-ads-automation

Made for: Claude Code.

Wrote 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.

agentmods badge for new-campaign

README.md
[![agentmods](https://agentmods.dev/badge/commands/shashankrai1983/fb-ads-automation/new-campaign/github.svg)](https://agentmods.dev/commands/shashankrai1983/fb-ads-automation/new-campaign)
Your own site
<a href="https://agentmods.dev/commands/shashankrai1983/fb-ads-automation/new-campaign"><img src="https://agentmods.dev/badge/commands/shashankrai1983/fb-ads-automation/new-campaign/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.

agentmods 80×15 button for new-campaign

Your own site · 80×15
<a href="https://agentmods.dev/commands/shashankrai1983/fb-ads-automation/new-campaign"><img src="https://agentmods.dev/badge/commands/shashankrai1983/fb-ads-automation/new-campaign.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,370 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.02370
Opus 5 $0.00000 $0.01185
Sonnet 5 $0.00000 $0.00474
Haiku 4.5 $0.00000 $0.00237

Measured 11d ago against content hash 43186e0f4572, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

new-campaign 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 11d 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.

.claude/commands/fb-ads/new-campaign.md · 287 lines

How it starts

The opening of the file, as written. The whole thing — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Interactive wizard to create a new Facebook ad campaign from scratch.

All entities are created in PAUSED status. Nothing goes live without explicit user approval.

Preamble: Load Knowledge Context

Before asking any questions, load client context to power recommendations:

  1. Read knowledge/accounts.md → identify available clients, their labels, currencies, and client directories
  2. Check which account is currently active via list_configured_accounts
  3. Ask which client this campaign is for (or confirm the active default)
  4. Set the correct account with set_default_account if needed
  5. Resolve the client directory from accounts.md (e.g., knowledge/clients/sunrise-cafe/)
  6. Read knowledge/clients/{client}/business-context.md → KPI targets, seasonality, audience, active campaigns, conversion channels
  7. Read knowledge/clients/{client}/brand-voice.md → copy guidelines, proven angles, CTA style (if it exists and has populated fields)
  8. Read knowledge/playbook.md → budget scaling rules, frequency thresholds
  9. enable_tools(groups="crud,targeting")
  10. get_all_campaign_insights(date_preset="last_30d") → current performance baselines (CPL, CTR, CPM, spend by campaign)

Store all loaded context mentally. If any file is missing or mostly TODO placeholders, note it and fall back to plain questions for that step.


Step 1: Campaign Objective

Analyze business-context.md (active objectives, conversion channels) and the last-30-day insights data, then present a recommendation:

## Step 1: Campaign Objective

Based on {client}'s business context:
- Business type: {from business-context.md}
- Active objectives: {from business-context.md campaign strategy}
- Conversion channels: {WhatsApp / Form / Website — from business-context.md}
- Best-performing objective (last 30d): {from insights — lowest CPL or highest CTR objective}

**Recommendation: {OUTCOME_X}**
Reason: {cite specific data — e.g., "Your lead campaigns average CPL $X
vs traffic at $Y. Lead generation is your strongest channel."}

Use this objective, or choose another?
(Traffic / Leads / Awareness / Engagement / Sales)

Read the full file on GitHub · 287 lines

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. 11d ago First seen · 287 lines · 0 tokens per session scan A 43186e0f4572

Subscribe to this mod's changes

new-campaign is a command published in the GitHub repository shashankrai1983/fb-ads-automation (0 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,370 tokens. 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-09-01.