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/activecampaign/activecampaign-plugin/campaign-reportgit clone --depth 1 https://github.com/ActiveCampaign/activecampaign-pluginWhat 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.00016 | $0.00664 |
| Opus 5 | $0.00008 | $0.00332 |
| Sonnet 5 | $0.00003 | $0.00133 |
| Haiku 4.5 | $0.00002 | $0.00066 |
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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/campaign-report
Generate a performance report for recent email campaigns.
Instructions
When the user runs /campaign-report, produce a comprehensive campaign performance summary.
Server rule: The MCP server does not compute aggregates. Report the per-campaign counts that
get_campaignreturns. Do not synthesize a blended "average open rate" or "total sends" across campaigns — present each campaign's own numbers and let the reader compare. If the user explicitly wants account-wide averages, tell them that lives in AC's native reporting.
Steps
-
Fetch recent campaigns: Use
list_campaignswith status "sent" to get the most recently sent campaigns. Default to the last 10 campaigns unless the user specifies a different range. (One call per turn; follownext_pageonly if you need more records to show.) -
Get per-campaign numbers: For each campaign, use
get_campaignto read the send count, open count, click count, bounce count, and unsubscribe count as the API returns them. Ifget_campaignreturns a rate directly, show it; if it returns only raw counts, show the counts — do not derive new rates from a population the server told you not to aggregate. -
Get link performance: For the few campaigns with the most clicks, use
get_campaign_linksto identify which links drove clicks. -
Present the report in this format:
## Campaign Performance Report
### Campaigns (Last [N], status: sent)
| Campaign | Sent Date | Sends | Opens | Clicks | Bounces | Unsubs |
|----------|-----------|-------|-------|--------|---------|--------|
| ... | ... | ... | ... | ... | ... | ... |
(Show each campaign's own counts exactly as returned. Include a rate column only if the API itself returned that rate.)
### Standouts
1. **[Campaign Name]** — highest opens/clicks in this set
- Top link: [URL] ([X] clicks)
### Patterns
- [Qualitative observation grounded in specific campaigns — e.g. "your three most recent sends each had fewer opens than the one before"]
### Recommendations
- [Specific, actionable suggestion tied to the records above]
### Not measured here
- Account-wide averages/rates aren't available via MCP — see AC's native campaign reporting for those.
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.
- 2d ago First seen · 58 lines · 16 tokens per session scan A 0aba2ddca5b3
campaign-report is a command published in the GitHub repository ActiveCampaign/activecampaign-plugin (0 stars, last pushed yesterday), licensed MIT. It adds 16 tokens to every session and 664 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.