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 daily-briefinggit 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/daily-briefing)<a href="https://agentmods.dev/skills/mondaycom/mcp/daily-briefing"><img src="https://agentmods.dev/badge/skills/mondaycom/mcp/daily-briefing.svg" alt="Measured on agentmods" 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 34 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.
- high Prompt Injection · line 492 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 84 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.00106 | $0.08352 |
| Opus 5 | $0.00053 | $0.04176 |
| Sonnet 5 | $0.00021 | $0.01670 |
| Haiku 4.5 | $0.00011 | $0.00835 |
Grade A, and why
daily-briefing 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 8d 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 — 666 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Morning Briefing
Produces a daily prioritized briefing over the user's monday CRM data and publishes it as a monday artifact — so the brief lives inside monday, not just in the chat.
Works for any monday CRM setup: pipeline users get deal buckets and pipeline totals; contacts/accounts users get relationship health and follow-up queues; lead managers get inbound lead status. If the user has no monday CRM board at all, the skill runs in standalone mode — ask for context, produce a useful brief from what they tell you.
When monday CRM features are in use, the brief automatically gets richer:
| monday CRM feature | What it adds | MCP access |
|---|---|---|
| Notetaker | Recent meeting notes matched to open deals or contacts | get_notetaker_meetings |
| Activity log | Logged calls, emails, and meetings on deals/contacts (last 48h) | get_board_activity + get_updates |
| Tasks / follow-ups | Items with a date column = today across deals or contacts board | get_board_items_page with date filter |
| Calendar sync (Outlook/Google) | Today's CRM-linked meetings | Not yet in MCP — skipped; wired when available (see workset status.md) |
| Email sync (Gmail/Outlook) | Tracked email threads on deals/contacts | Not yet in MCP — skipped; logged emails accessible today via get_updates on contacts/deals |
monday CRM's calendar and email sync features exist in the product but are not fully exposed via the MCP connector yet. The skill attempts to reach them via
all_monday_apiraw GraphQL. If the data isn't there, it notes the gap in the brief and skips the section — it does not error out.
Flow: Connector check → Mode → Connector discovery → Board detection → Board type → Data pull → Synthesize → Publish → Share (opt-in) → Proactive (opt-in).
Input
- Optional: board name or ID via argument.
- Optional: mode override (Default / Silent / Proactive) via project instructions or one-shot prompt.
Output
- α (default): A monday update on a pinned "My Morning" item OR a new doc in the user's personal workspace, titled
Morning Briefing — <weekday>, <Mon DD>. Body carries theGenerated by Claudefooter + an HTML comment<!-- claude-skill-id: daily-briefing -->for idempotency. Markdown brief printed in chat as a mirror. - β (Share mode, opt-in): Notification to manager + update on team-rollup board.
- Proactive extension (opt-in): Per-item
create_updateon stalled records;create_notificationfor commitments due today. - Standalone mode (no board): Brief printed in chat only — no monday artifact (nothing to publish to).
What ships with it
2 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.
- 8d ago First seen · 666 lines · 106 tokens per session scan A 3fa9ef85089d
daily-briefing is a skill published in the GitHub repository mondaycom/mcp (422 stars, last pushed today), licensed MIT. It adds 106 tokens to every session and 8,352 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.