Security audit
Security checks across malware telemetry and agentic risk
This Sequenzy guide is mostly legitimate documentation, but it tells agents to perform a permanent campaign cancellation before clarifying intent.
Install only if you are comfortable with an agent operating Sequenzy production workflows. Require the agent to inspect the exact resource and get explicit confirmation before canceling campaigns, deleting resources, changing subscribers/lists, inviting teammates, creating API keys, or changing webhooks.
- segments `list`, `create`, `update`, `delete`, and `count`, including `--match any`, nested filter roots, custom event filters, and saved-segment composition filters - templates `list`, `get`, `create`, `update`, and `delete`, with `list` supporting label filters and `create`/`update` accepting labels, raw HTML, or Sequenzy block JSON - campaigns `list`, `get`, `create`, `update` including label and reply-to updates, `schedule`, and `test`, with `list` supporting label filters, `create` accepting labels plus raw HTML, Sequenzy block JSON, or prompt-generated content, `update` accepting labels plus raw HTML or Sequenzy block JSON, and `schedule` returning a review preview link - campaign lifecycle control with `campaigns cancel` (stops scheduled, paused, waiting-approval, or sending campaigns immediately, no confirmation prompt), `campaigns pause` and `campaigns resume` for an active send (resume supports `--spread-over-hours`), `campaigns delete` (blocked while sending, scheduled, or paused - cancel first), and `campaigns duplicate` with `--mode campaign|ab_test|variant` - ab-tests `list`, `get`, `stats`, `restart`, `update-variant`, `create`, `add-variant`, `delete-variant`, and `delete`; create/add-variant/delete-variant/delete work on campaign A/B tests in draft status, variant A is the protected control, and `restart` reruns a finished sequence A/B test - MCP template and campaign tools support labels on list/create/update; MCP `update_campaign` also supports `replyTo` and `replyProfileId`, and MCP `schedule_campaign` schedules draft or already scheduled campaigns - MCP `search_subscribers` supports list filters through `list`, `listId`, or `listName`; MCP `add_subscribers_to_list` accepts up to 500 emails per call
- `campaigns get` now includes saved reply-to details when the campaign has a reply profile - only draft campaigns can be updated through this API path - there is no CLI command for immediate send; schedule with a near-future `--at` timestamp instead - `cancel` works from scheduled, sending, paused, waiting_approval, and rejected statuses; it shows no confirmation prompt so a bad send can be stopped fast - `pause` only works on a campaign in sending status; `resume` only works on a paused campaign - `resume --spread-over-hours` accepts integers from 1 to 72 to spread the remaining delivery - `delete` is blocked while the campaign is sending, scheduled, or paused; cancel it first
- use `cancel` when the send should not continue at all; it is permanent and works from scheduled, sending, paused, waiting-approval, and rejected statuses - use `pause` when the user wants to stop a send temporarily and may continue it; it only works while the campaign is in sending status - use `resume` to continue a paused campaign, optionally spreading the remaining delivery with `--spread-over-hours` (1-72) - `cancel` needs no `--yes` and shows no confirmation prompt, so it is the fastest way to stop a bad send; run it first and ask questions after when the user reports a mistake - check `campaigns get` first when you are unsure of the current status; the API rejects transitions from the wrong status MCP equivalents are `cancel_campaign`, `pause_campaign`, and `resume_campaign` (optional `spreadOverHours`).
64/64 vendors flagged this skill as clean.
No suspicious patterns detected.
