campaign-report

campaign-report is a command for Claude Code from windsor-ai/claude-windsor-ai-plugin. It costs 14 tokens per session (187 once invoked), scanned A, original, MIT.

A command that creates a campaign performance report from a connected advertising or business-data source. A campaign is a tracked marketing effort, and the report covers its recent results.

In plain words
What is it for?
Use it to report the last 30 days of campaign data, sort campaigns by spending, and show totals for spending, clicks, and conversions.
Why use it?
It avoids manually collecting spending, clicks, views, conversions, and revenue from the source and arranging them into a summary.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the claude-windsor-ai-plugin plugin — 1 skill, 3 commands, 1 agent shipped together

Good fit Use it to report the last 30 days of campaign data, sort campaigns by spending, and show totals for spending, clicks, and conversions.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/windsor-ai/claude-windsor-ai-plugin/campaign-report
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.

Clone the repo
git clone --depth 1 https://github.com/windsor-ai/claude-windsor-ai-plugin

Made for: Claude Code.

Or install claude-windsor-ai-plugin, the plugin that ships this one along with the rest of its 1 skill, 3 commands, 1 agent.

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 campaign-report

README.md
[![agentmods](https://agentmods.dev/badge/commands/windsor-ai/claude-windsor-ai-plugin/campaign-report/github.svg)](https://agentmods.dev/commands/windsor-ai/claude-windsor-ai-plugin/campaign-report)
Your own site
<a href="https://agentmods.dev/commands/windsor-ai/claude-windsor-ai-plugin/campaign-report"><img src="https://agentmods.dev/badge/commands/windsor-ai/claude-windsor-ai-plugin/campaign-report/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 campaign-report

Your own site · 80×15
<a href="https://agentmods.dev/commands/windsor-ai/claude-windsor-ai-plugin/campaign-report"><img src="https://agentmods.dev/badge/commands/windsor-ai/claude-windsor-ai-plugin/campaign-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 187 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.00014 $0.00187
Opus 5 $0.00007 $0.00093
Sonnet 5 $0.00003 $0.00037
Haiku 4.5 $0.00001 $0.00019

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

Security

Grade A, and why

campaign-report 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 10d 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/campaign-report.md · 19 lines

What it actually says

/campaign-report

Generate a quick campaign performance report from any connected data source.

Instructions

  1. Call get_connectors to list the user's connected platforms and accounts.
  2. Ask the user which connector and account to report on (or pick the most obvious one if there's only one).
  3. Call get_data with these fields: ["campaign", "date", "spend", "clicks", "impressions", "conversions", "revenue"] and date_preset: "last_30d".
  4. Format the results as a clean markdown table sorted by spend descending.
  5. Include a summary line with totals for spend, clicks, and conversions.

If the connector doesn't support some of those fields, call get_options first and adapt to available fields.

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. 10d ago First seen · 19 lines · 14 tokens per session scan A 35ef7c05b6a6

Subscribe to this mod's changes

campaign-report is a command published in the GitHub repository windsor-ai/claude-windsor-ai-plugin (0 stars, last pushed 28d ago), licensed MIT. It adds 14 tokens to every session and 187 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.