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 workspace-buildergit 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/workspace-builder)<a href="https://agentmods.dev/skills/mondaycom/mcp/workspace-builder"><img src="https://agentmods.dev/badge/skills/mondaycom/mcp/workspace-builder/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/workspace-builder"><img src="https://agentmods.dev/badge/skills/mondaycom/mcp/workspace-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 21 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- medium Excessive Agency · line 18 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 155 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00107 | $0.06351 |
| Opus 5.5 | $0.00043 | $0.02540 |
| Sonnet 5.5 | $0.00021 | $0.01270 |
| Haiku 4.5 | $0.00011 | $0.00635 |
Grade A, and why
workspace-builder 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 — 434 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workspace Builder
Sets up a CRM workspace conversationally — turning "I don't know how to start" into a working board on day 1. Replaces the manual template-pick → column-rename → column-add → group-rename loop that gates 442 median days between CRM install and first MCP execution. This is the single highest-leverage retention skill in the catalog.
Flow: Trigger → Discover → Propose → Confirm → Build (α) → Seed (β, opt-in) → Handoff.
Input
- Optional: business description via argument.
- Optional: user pre-declared mode (Default / Silent / Proactive). Add "silently" or "skip confirmations" to your request to run in Silent mode. Silent mode builds without per-step confirmations.
Output
- α (default): One board (or set of boards) created in the user's chosen workspace. Boards carry the user's chosen names (no plugin prefix). Groups + columns scaffolded per the proposed structure. A
CRM Setup — <Mon DD>doc summarizes what was created and what's next, withGenerated by Claude · <ISO timestamp>+<!-- claude-skill-id: workspace-builder -->in the body. - β (Seed mode, opt-in): 5–10 example items per board so the user can see the shape with data, not just empty columns. Each example item carries
Source = Claudeon a status column (auto-create the column with user confirm if missing) — no[Example]prefix on names. - Proactive extension: Out of scope for v0.1 (automation creation requires
create_automation_rule, not yet shipped). The setup doc includes a deep-link to the in-product Automation Recipes UI for that step.
Knowledge
- monday CRM entity board catalog + relationships (§ monday CRM Entity Boards).
- Industry → board-shape map (§ Step 3).
- Column-type repertoire (§ Step 4).
- Shared artifact conventions (§ Shared patterns).
- GraphQL mutations for group operations:
references/monday-graphql-mutations.md.
Tools (MCP)
get_user_context— resolve user + existing workspaces.list_workspaces/workspace_info— find a target workspace.search— confirm we aren't duplicating an existing CRM board.create_workspace— only if the user explicitly wants a new workspace.create_board— the core write.create_group— pipeline stages as groups (or as status labels — see Step 4).create_column— typed columns per the proposed schema.create_item— β seed items.create_doc— publish the setup summary doc.all_monday_api— group rename/delete mutations + column settings (status labels, number units) not exposed by wrapped tools. Seereferences/monday-graphql-mutations.mdfor exact payloads.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 434 lines · 107 tokens per session scan A 9511e03cf2f7
workspace-builder is a skill published in the GitHub repository mondaycom/mcp (433 stars, last pushed today), licensed MIT. It adds 107 tokens to every session and 6,351 once invoked, about $0.0004 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
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.
paseo
Paseo reference for managing projects, workspaces, workspace scripts, agents, schedules, and heartbeats.
testgen-flow
Workflow for generating test cases from requirements (Issue Tracker / Wiki sources), exporting to a Test Management System, etc.
backlog
To validate story readiness for a sprint or to break work into a human WBS.