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/sendx/email-skills/api-campaign-buildernpx skills add sendx/email-skills --skill api-campaign-buildergit clone --depth 1 https://github.com/sendx/email-skillsWrote 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/sendx/email-skills/api-campaign-builder)<a href="https://agentmods.dev/skills/sendx/email-skills/api-campaign-builder"><img src="https://agentmods.dev/badge/skills/sendx/email-skills/api-campaign-builder.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.00021 | $0.03091 |
| Opus 5 | $0.00010 | $0.01545 |
| Sonnet 5 | $0.00004 | $0.00618 |
| Haiku 4.5 | $0.00002 | $0.00309 |
Grade A, and why
api-campaign-builder scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST https://api.sendx.io/api/v1/rest/sender \ How it starts
The opening of the file, as written. The whole thing — 367 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Campaign Builder
What you do
You help developers and technical marketers use the SendX API to create HTML email campaigns, schedule them for review or immediate sending, and monitor delivery. You translate marketing goals into working API calls — with correct authentication, entity references, and scheduling logic.
When to activate
- "How do I create a campaign via the API?"
- "I need to schedule an email through SendX's API"
- "Set up a campaign that goes to my approval queue first"
- "Send an HTML email to a list using the API"
- "How do I check if my campaign was sent?"
- "Create a campaign but don't send it yet"
- Any request involving SendX REST endpoints for campaigns, senders, or templates
Your expertise
Authentication
Every request needs your team API key in the header:
X-Team-ApiKey: YOUR_API_KEY
Base URL: https://api.sendx.io/api/v1/rest
All requests use Content-Type: application/json.
Entity ID prefixes
SendX IDs follow a predictable pattern. Always use the full prefixed ID:
| Entity | Prefix | Example |
|---|---|---|
| Campaign | campaign_ |
campaign_abc123def456 |
| Sender | sender_ |
sender_xyz789ghi012 |
| List | list_ |
list_mno345pqr678 |
| Tag | tag_ |
tag_stu901vwx234 |
| Template | template_ |
template_yza567bcd890 |
| Segment | segment_ |
segment_efg123hij456 |
The campaign creation workflow
Follow this order every time:
1. Create or fetch a Sender
2. Create or fetch a Template (optional — you can inline HTML)
3. Create the Campaign (with targeting + schedule settings)
4. Check status via Report endpoint
Step 1 — Sender
Create a sender:
curl -X POST https://api.sendx.io/api/v1/rest/sender \
-H "X-Team-ApiKey: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "Marketing Team",
"email": "[email protected]",
"replyTo": "[email protected]"
}'
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.
- 5d ago First seen · 367 lines · 21 tokens per session scan A a13cfc165c4d
api-campaign-builder is a skill published in the GitHub repository sendx/email-skills (8 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 3,091 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
email-marketing-bible
Data-backed email marketing skill for AI agents. Use when building or running email automation, driving an ESP from an agent (MCP/connectors), diagnosing deliverability, writing or de-slopping email copy, designing emails, choosing a platform, or pulling benchmarks. Covers AI email automation, flows, deliverability…
Infrastructure Drift Detection
Detecting and testing infrastructure drift between desired state and actual state using automated scanning, alerting, and remediation patterns.
custom-builtin-functions
Create a custom builtin function to be used in the Rego policy engine.
port-mass-scan
Port scan /8-/24 with Masscan+RustScan and nmap banners.
biome
Repository guidance for using Biome as the formatter, linter, and code quality tool within the hr-skills monorepo.
cis-aws-compute-2.4
Ensure an Organizational EC2 Tag Policy has been Created.