A setup command for an Adspirer brand workspace, where campaign and advertising information is managed. It connects the workspace and gathers brand documents and campaign data.

Authenticating the Adspirer connection, scanning local brand documents, and pulling campaign data into the workspace.

It gives the workspace the connections and local information needed before working with a brand's advertising campaigns.

setup — Command by amekala

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/amekala/ads-mcp/setup

Clone the repo

git clone --depth 1 https://github.com/amekala/ads-mcp

Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 670 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.

Model	Per session	Once invoked
Fable 5	$0.00015	$0.00670
Opus 5	$0.00008	$0.00335
Sonnet 5	$0.00003	$0.00134
Haiku 4.5	$0.00002	$0.00067

Measured yesterday against content hash 28eac62424b7, 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 yesterday.

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 · 26 lines

What it actually says

IMPORTANT: You may execute this workflow directly or delegate parts to the single performance-marketing-agent subagent. Keep responsibility for final output in this command and ensure all required checks are completed.

Run the full brand workspace setup. Follow these steps in order:

Connect to Adspirer — Call get_connections_status.
- If it works: continue to step 2.
- If the MCP server is not found: tell the user "Run /mcp and find the adspirer server (listed under the plugin, e.g. plugin:adspirer-advertising-agent:adspirer) — click to authenticate. If you don't see it, run /plugin marketplace add amekala/ads-mcp then /plugin install adspirer-advertising-agent. After authenticating, run /adspirer:setup again."
- As a fallback: run claude mcp add --transport http adspirer https://mcp.adspirer.com/mcp via Bash, then tell the user to restart Claude Code, run /mcp to authenticate, then run /adspirer:setup again.
- If the MCP server is registered but not authenticated: tell the user "Run /mcp, find the Adspirer server, and authenticate it. Then run /adspirer:setup again."
Scan local folder for brand docs — use Glob to find files: **/*.md, **/*.txt, **/*.csv, **/*.yaml, **/*.json, **/*.pdf. Read any files found.
Pull live campaign data from the platforms that came back connected. Follow adspirer-mcp for the call contract.

Direct calls:
- get_connections_status — run this first; skip any platform it reports as not connected
- get_campaign_performance (lookback_days: 30)
- get_meta_campaign_performance (lookback_days: 30)
Through a router, with {"action": "execute", "tool_name": "...", "arguments": {...}}:
- google_ads → list_campaigns, get_business_profile, get_benchmark_context
- linkedin_ads → list_linkedin_campaigns, get_linkedin_campaign_performance (lookback_days: 30)
Create CLAUDE.md at the project root with: brand context from scanned docs, connected platforms and account info, performance snapshot with key metrics, KPI targets. Existing-file guard: if a CLAUDE.md already exists and is not an Adspirer brand workspace (e.g. it's a software project's instructions), never overwrite or restructure it — ask the user whether to append a clearly-marked ## Adspirer Brand Context section instead, and don't touch the file until they answer. If it's already a brand workspace, update it in place preserving user edits.
Present a summary of everything found — accounts connected, campaigns discovered, key metrics, and what you can help with

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.

yesterday First seen · 26 lines · 15 tokens per session scan A 28eac62424b7

Subscribe to this mod's changes

setup is a command published in the GitHub repository amekala/ads-mcp (86 stars, last pushed 16d ago), licensed MIT. It adds 15 tokens to every session and 670 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.

advertising ai-agent chatgpt claude google-ads linkedin-ads

setup

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

audit

analyze

awesome-chatgpt

design-review

setup-pm-skills

ship-an-mcp-server