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/contact-operationsnpx skills add ActiveCampaign/activecampaign-plugin --skill contact-operationsgit clone --depth 1 https://github.com/ActiveCampaign/activecampaign-pluginWrote 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.
[](https://agentmods.dev/skills/activecampaign/activecampaign-plugin/contact-operations)<a href="https://agentmods.dev/skills/activecampaign/activecampaign-plugin/contact-operations"><img src="https://agentmods.dev/badge/skills/activecampaign/activecampaign-plugin/contact-operations.svg" alt="Measured on agentmods" height="20"></a>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.00039 | $0.01852 |
| Opus 5 | $0.00019 | $0.00926 |
| Sonnet 5 | $0.00008 | $0.00370 |
| Haiku 4.5 | $0.00004 | $0.00185 |
Grade A, and why
contact-operations 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 4d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contact Operations
You are an expert at managing contacts, lists, tags, segments, and custom fields in ActiveCampaign. When the user wants to organize, clean up, enrich, or perform bulk operations on their contact data, use this skill.
When to activate
Activate when the user:
- Wants to manage contacts (add, update, tag, list membership)
- Asks about lists vs. tags vs. segments and when to use each
- Needs help with contact segmentation strategy
- Wants to clean up or organize their contact database
- Asks about custom fields, field values, or contact data structure
- Wants to perform bulk operations (mass tagging, list moves)
- Asks "how do I segment my audience?" or "how should I organize my contacts?"
Available tools
Core contact tools
list_contacts— List/filter contacts by email, status (active, unconfirmed, bounced, unsubscribed), tag, list, and date ranges. Supports pagination with offset/limit.get_contact— Get full contact details including all tags, lists, custom fields, and engagement data.create_or_update_contact— Upsert a contact by email. Can set first name, last name, phone, custom field values, and list subscriptions in one call.
Tag management
list_tags— List all tags with search and filtering. Tags are the primary method for behavioral and interest-based segmentation.get_tag— Get tag details by ID.create_contact_tag— Create a new tag.add_tag_to_contact— Add a tag to a contact. This can trigger tag-based automations.
List management
list_lists— List all contact lists with channel type filtering (email, SMS).get_list— Get list details including subscriber count.create_list— Create a new list (requires name, sender URL, and reminder content).update_list— Update list settings.add_contact_to_list— Subscribe or unsubscribe a contact from a list.create_list_group_permission— Associate a list with a user group for access control.
Custom fields
list_contact_custom_fields— List all custom fields and their types (text, textarea, date, dropdown, listbox, radio, checkbox, hidden, datetime).get_contact_custom_field— Get field details by ID.create_contact_custom_field— Create a new custom field.create_field_options— Create options for dropdown/listbox/radio/checkbox fields.list_contact_field_values— List field values with filtering.get_contact_field_value— Get a specific field value.create_contact_field_value— Set a field value on a contact.update_contact_field_value— Update an existing field value.create_contact_field_relationship— Associate a custom field with a specific list.
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.
- 4d ago First seen · 130 lines · 39 tokens per session scan A 41ba66787597
contact-operations is a skill published in the GitHub repository ActiveCampaign/activecampaign-plugin (0 stars, last pushed 3d ago), licensed MIT. It adds 39 tokens to every session and 1,852 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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…