weekly-digest

A command that creates a weekly summary of activity in ActiveCampaign, a marketing platform, covering campaigns, automations, contacts, and deals.

In plain words
What is it for?
Use it to review campaigns sent, active automations, recently added contacts, and deal activity from the last seven days.
Why use it?
It brings recent marketing activity into one report while keeping the individual figures returned by ActiveCampaign instead of inventing combined totals.

Command

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/activecampaign/activecampaign-plugin/weekly-digest
Clone the repo
git clone --depth 1 https://github.com/ActiveCampaign/activecampaign-plugin
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 776 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.

ModelPer sessionOnce invoked
Fable 5 $0.00019 $0.00776
Opus 5 $0.00010 $0.00388
Sonnet 5 $0.00004 $0.00155
Haiku 4.5 $0.00002 $0.00078

Measured 2d ago against content hash 46e4d734c73e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

weekly-digest 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.

commands/weekly-digest.md · 81 lines

How it starts

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

/weekly-digest

Generate a weekly marketing digest summarizing activity across campaigns, automations, contacts, and deals.

Instructions

When the user runs /weekly-digest, produce a comprehensive weekly summary of their ActiveCampaign activity.

Server rule: The MCP server does not compute aggregates or totals. Report the counts and per-record numbers the tools return. Do not sum deal values into a "total pipeline value", average campaign rates, or tally "contacts completed this week" by paging the whole dataset. Where you can only show records (not a total), show the records and say so. Point users to AC's native reporting for true roll-ups.

Steps

  1. Campaign activity: Use list_campaigns to find campaigns sent in the last 7 days. For a notable one, use get_campaign to read its returned counts. Show each campaign's own numbers — don't blend them.

  2. Automation activity: Use list_automations to list active automations and the entered/completed counts carried on each record.

  3. Contact growth: Use list_contacts with date filters to find contacts added in the last 7 days (show the count the query returns / the records). Use list_lists for list names and the subscriber counts the API returns per list.

  4. Deal activity: Use list_deals filtered by status and date to show deals created / won / lost in the window as records, sorted by value where useful. Use list_deal_pipelines / list_deal_stages for pipeline context. Do not total the values — list the deals.

  5. Present the digest in this format:

## Weekly Marketing Digest
**Week of [Date Range]**

---

### Campaigns Sent ([N] this week)
| Campaign | Date | Sends | Opens | Clicks |
|----------|------|-------|-------|--------|
| ...      | ...  | ...   | ...   | ...    |
(Counts as returned by the API. Include a rate column only if the API returned it.)

**Most opens/clicks this week**: [Campaign Name]

---

### Automations
- **Active automations**: [N]
- Notable per-automation movement this week (from the records): [e.g. "Welcome series — 40 entered"]

---

### Contacts
- **New contacts this week**: [N returned by the dated query]
- **Lists**: [list name — subscriber count as returned], …

---

### Deals (last 7 days)
| Deal | Status | Value | Stage |
|------|--------|-------|-------|
| ...  | won/open/lost | [as returned] | ... |
(Individual deals — not summed. For total pipeline value, see AC's native deal reporting.)

---

### Key Takeaways
1. [Most notable thing that happened, grounded in the records above]
2. [Area worth attention]
3. [Suggested action for next week]

### Not measured here
- Totals, averages, and blended rates aren't available via MCP — see AC's native reporting.

Read the full file on GitHub · 81 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. 2d ago First seen · 81 lines · 19 tokens per session scan A 46e4d734c73e

Subscribe to this mod's changes

weekly-digest is a command published in the GitHub repository ActiveCampaign/activecampaign-plugin (0 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 776 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.