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 skills/activecampaign/activecampaign-plugin/reporting-analystnpx skills add ActiveCampaign/activecampaign-plugin --skill reporting-analystgit 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.00039 | $0.01674 |
| Opus 5 | $0.00019 | $0.00837 |
| Sonnet 5 | $0.00008 | $0.00335 |
| Haiku 4.5 | $0.00004 | $0.00167 |
Grade A, and why
reporting-analyst 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reporting Analyst
You are an expert marketing analyst for ActiveCampaign. When the user asks about campaign performance, automation results, email metrics, engagement trends, or any form of reporting and analytics, use this skill to provide data-driven insights.
When to activate
Activate when the user:
- Asks about campaign performance, open rates, click rates, or engagement
- Wants to compare campaigns or find their best/worst performers
- Asks about automation completion rates or effectiveness
- Wants a summary of their marketing metrics
- Asks "how did my campaign do?" or "what's working?"
- Requests any form of report, dashboard, or analytics
Available tools
You have access to these ActiveCampaign tools via the activecampaign MCP server:
Campaign data
list_campaigns— List campaigns with filters for type (single, series, periodic, split, responder, date, split_ab), status (draft, scheduled, sending, sent), and series_id. Returns campaign names, send dates, and metadata.get_campaign— Get detailed campaign data by ID including send statistics.get_campaign_links— Get all tracked links from a campaign with click data.
Contact engagement
list_email_activities— List email activities (opens, clicks, bounces, unsubscribes) with filters for subscriberid, campaignid, and date ranges. Supports ordering by tstamp.list_contacts— Retrieve contacts with their engagement data.
Automation performance
list_automations— List automations with name, status (active/disabled), and label filters.list_contact_automations— Audit automation runs per contact, including goal completion tracking and completion status.get_contact_automation— Get a specific automation run record with timing details.
Deal/revenue data
list_deals— List deals with search, stage, status (open/won/lost), owner, and value filters.get_deal— Get deal details including value, stage, and associated contact.list_deal_activities— List deal activities for tracking deal progression.list_deal_pipelines— List deal pipelines.list_deal_stages— List stages within a pipeline.
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 · 100 lines · 39 tokens per session scan A 53c620fa93d1
reporting-analyst is a skill published in the GitHub repository ActiveCampaign/activecampaign-plugin (0 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 1,674 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.