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 skills add mondaycom/mcp --skill run-sequencegit clone --depth 1 https://github.com/mondaycom/mcpWrote 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/mondaycom/mcp/run-sequence)<a href="https://agentmods.dev/skills/mondaycom/mcp/run-sequence"><img src="https://agentmods.dev/badge/skills/mondaycom/mcp/run-sequence/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mondaycom/mcp/run-sequence"><img src="https://agentmods.dev/badge/skills/mondaycom/mcp/run-sequence.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00133 | $0.03183 |
| Opus 5.5 | $0.00053 | $0.01273 |
| Sonnet 5.5 | $0.00027 | $0.00637 |
| Haiku 4.5 | $0.00013 | $0.00318 |
Grade A, and why
run-sequence 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 1mo 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 — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run Sequence
Flow: Trigger → Detect intent → Resolve board/sequence/contact → Execute → Confirm + report.
Input
- Optional: action + target via argument (e.g., "enroll Acme in welcome sequence").
- If no argument: ask what they want to do.
Output
- List: sequences on a board with status, step count, enrollment counts, analytics.
- Create: new sequence scaffolded via the tool's built-in gate flow (board → steps → email sender if needed), starts INACTIVE.
- Enroll: one or more CRM items enrolled in a sequence; returns succeeded/failed counts.
- Activate/Deactivate: sequence state toggled with confirmation. Deactivate does NOT stop existing enrollments — only blocks new ones.
- Duplicate: copy of a sequence created in INACTIVE state.
- Analyze: per-run + level + step funnel (reply rate, open rate, click-through).
- Contact journey: all sequences a contact is enrolled in, sorted by most recent.
Knowledge
- Sequence states: ACTIVE (enrolling + running), INACTIVE (not enrolling; existing runs continue).
deactivate-sequence≠ pause — enrolled contacts keep progressing; only new enrollments are blocked.- No sequence editing tool exists — steps cannot be added/modified via MCP. Direct users to Tools → Sequences in the UI.
get-board-sequencesrequires aboard_id— always resolve the board first.create-sequencehas a built-in gate system: call it with what you have; if anything's missing the tool returnsCONFIRMATION_REQUIREDwith exact instructions — follow them verbatim, never pre-empt the gates.enroll-item-in-sequencetakesboard_id,sequenceId, anditemIds(array of string IDs).
Tools (MCP)
get-board-sequences— list sequences on a board (needsboard_id).get-sequence-analytics— per-run, level, and step analytics for one sequence.get-contact-journey— all sequences a contact/item is enrolled in (needsboard_id+item_id).enroll-item-in-sequence— enroll one or more items in a sequence.activate-sequence— INACTIVE → ACTIVE.deactivate-sequence— ACTIVE → INACTIVE (existing enrollments continue).duplicate-sequence— copy a sequence; new copy starts INACTIVE.create-sequence— create a new sequence; call directly with whatever args you have.get-connected-email-accounts— list linked Gmail/Outlook accounts; used whencreate-sequencegate requires a sender.get_user_context— user identity + account.search/get_board_info/get_board_items_page— resolve boards and items by name.
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.
- 1mo ago First seen · 246 lines · 133 tokens per session scan A a99e98a528d7
run-sequence is a skill published in the GitHub repository mondaycom/mcp (433 stars, last pushed today), licensed MIT. It adds 133 tokens to every session and 3,183 once invoked, about $0.0005 per session on Opus 5.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
agents-sdk-dotnet
Use when any code imports Microsoft.Agents.Hosting.AspNetCore, Microsoft.Agents.Builder, or related Agents SDK packages, or when the user is building, configuring, or asking questions about a Microsoft 365 Agents SDK agent in C# / .NET. Trigger on questions about appsettings.json, connection configuration…
agents-sdk-dotnet-otel
Use when adding, configuring, validating, or troubleshooting OpenTelemetry observability for a Microsoft 365 Agents SDK application in C# / .NET. Trigger when the user mentions OpenTelemetry, OTel, telemetry, traces, metrics, logs, OTLP, Aspire Dashboard, Application Insights, Azure Monitor, distributed tracing…
bf-to-agents-sdk-dotnet-migration
Use when migrating a Bot Framework .NET SDK bot to Microsoft 365 Agents SDK. Triggered by projects that depend on packages: Microsoft.Bot.Builder or Microsoft.Bot.Builder.Integration.AspNet.Core that want to migrate to Agents SDK.
teams-app-manifest
Create or audit a Microsoft Teams app manifest for an existing Microsoft 365 Agents SDK application by mapping declared intent and source-code evidence to released manifest capabilities. Use when manifest.json is missing, incomplete, or must be checked against implemented Teams features. Does not configure Microsoft…
agents-sdk-dotnet-debugging
Use when troubleshooting an agent built with the Microsoft Agents SDK (Microsoft.Agents.Hosting.AspNetCore and related packages) in C# / .NET. Trigger on any of these symptoms: build or C# compile errors, crashes on startup, 401 or auth errors on incoming requests, the bot not responding to messages, appsettings.json…
github-review-pr
Review GitHub pull requests with detailed, multi-perspective code analysis using parallel subagents. Use this skill whenever the user wants to review a PR, asks for code review on a pull request, mentions "review PR", "check this PR", "look at pull request", or references a PR number or GitHub PR URL. Do NOT use for…