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 automate-crmgit 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/automate-crm)<a href="https://agentmods.dev/skills/mondaycom/mcp/automate-crm"><img src="https://agentmods.dev/badge/skills/mondaycom/mcp/automate-crm/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/automate-crm"><img src="https://agentmods.dev/badge/skills/mondaycom/mcp/automate-crm.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.00099 | $0.01649 |
| Opus 5 | $0.00049 | $0.00825 |
| Sonnet 5 | $0.00020 | $0.00330 |
| Haiku 4.5 | $0.00010 | $0.00165 |
Grade A, and why
automate-crm 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 9d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Automate CRM
Flow: Detect intent → Resolve board → Describe automation → Create / List / Manage → Confirm
Input
- Optional: automation description via argument (e.g., "notify owner when Stage = Won").
- Optional: board name or type (Deals, Contacts, Leads).
Output
- Create: active automation on the target board, confirmed with a summary of what it does.
- List: formatted table of automations currently active on the board.
- Manage: automation activated, deactivated, or deleted, with confirmation.
Knowledge
Most common CRM automations (by account usage)
| Trigger | Action | Accounts |
|---|---|---|
| Status changes to something | Move item to group | 9,821 |
| Status changes to something | Notify someone | 6,482 |
| Status changes to something | Set date | 6,341 |
| Item created | Notify someone / assign / set date | 10,019 |
| Date arrives | Notify / change status | 4,972 |
| Button clicked | Any action | 3,015 |
| Status changes from X to Y | Move / notify | 1,721 |
The dominant CRM pattern: status change → move to group. When in doubt, this is what most users want.
Automations vs. Workflows
- Automations (
create_automation) — board-scoped trigger/action rules. Active immediately on creation. Use for CRM daily operations. - Workflows (
create_workflow) — workspace-level, cross-board objects. Start as drafts; must be published. Use only when explicitly asked.
Known limitations
- No date arithmetic. Engine only accepts static dates — cannot compute "7 days from today". Offer
todayas fallback or a periodic trigger. - Column resolution. Tool matches columns by semantic similarity. If a column doesn't exist, the tool returns
needs_clarification. - One trigger per automation.
- Legacy automations are read-only —
list_automationsreturns them but they cannot be modified via MCP.
needs_clarification response
When create_automation returns needs_clarification, present each unresolvedField with available options, collect the answer, then retry.
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.
- 9d ago First seen · 161 lines · 99 tokens per session scan A 4eace5cb2ab0
automate-crm is a skill published in the GitHub repository mondaycom/mcp (423 stars, last pushed yesterday), licensed MIT. It adds 99 tokens to every session and 1,649 once invoked, about $0.0005 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
init-workspace-flow
Workflow for initializing or upgrading a workspace: context, discovery, documentation, etc.
arrange-workspace-flow
Workflow for arranging a workspace: layout, reference source code, business/technical context, ecosystem setup.
github-triage
Triage GitHub issues through a label-based state machine with interactive grilling sessions. Use when user wants to triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
testgen-flow
Workflow for generating test cases from requirements (Issue Tracker / Wiki sources), exporting to a Test Management System, etc.
paseo
Paseo reference for managing projects, workspaces, workspace scripts, agents, schedules, and heartbeats.
backlog
To validate story readiness for a sprint or to break work into a human WBS.