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 agentmods add skills/mondaycom/mcp/log-activitynpx skills add mondaycom/mcp --skill log-activitygit clone --depth 1 https://github.com/mondaycom/mcpWhat 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 | $0.00111 | $0.02462 |
| Opus 5 | $0.00056 | $0.01231 |
| Sonnet 5 | $0.00022 | $0.00492 |
| Haiku 4.5 | $0.00011 | $0.00246 |
Grade A, and why
log-activity 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 2d 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Log Activity
Flow: Trigger → Detect intent (log / read / update) → Resolve CRM item → Gather activity details → Execute → Confirm.
Input
- Optional: activity description via argument (e.g., "call with Acme about renewal").
- Optional: CRM item name or identifier if mentioned.
Output
- Log (create): structured activity record (call, meeting, note) on the target item's timeline, with confirmation.
- Read: formatted activity history for the specified item and time range.
- Update: edited timeline entry with confirmation of changes.
Knowledge
- Timeline = the activity feed on any CRM item (deal, contact, lead, account).
- Activity types: calls, meetings, notes, emails (read-only from timeline), custom types per account.
- For aggregated stats (team totals, rep comparisons), use the activity-insights skill —
get-activity-insightsis more efficient than counting raw timeline items. - Timeline items are append-only in the UI; the API allows updates to existing entries.
update-timeline-itemvisibility on external connector is unconfirmed — degrade gracefully if it fails.
Tools (MCP)
get-custom-activities— list activity types configured on the account (call, meeting, note, custom).get-timeline-items— read an item's timeline (activities, emails, notes).create-timeline-item— log a structured activity (call, meeting) with type, date, attendees, notes.update-timeline-item— edit an existing timeline activity's content.create-timeline-note— add a free-text note to an item's timeline.get_user_context— user identity for attribution.search/get_board_info/get_board_items_page— resolve CRM items by name or company.
Cross-skill handoffs
- From meeting-to-opportunity: after a meeting recap, suggest logging the meeting as a structured activity on the deal.
- From run-sequence: when a sequence triggers a manual call step, suggest logging the call outcome.
- To morning-briefing: logged activities feed the daily brief's "recent activity" section.
- From daily-briefing: brief surfaces items with no activity in N days → suggest logging.
- To activity-insights: when the user asks about team totals or rep comparisons rather than a specific item's history.
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.
- 2d ago First seen · 215 lines · 111 tokens per session scan A d71ee5d624c2
log-activity is a skill published in the GitHub repository mondaycom/mcp (421 stars, last pushed 6d ago), licensed MIT. It adds 111 tokens to every session and 2,462 once invoked, about $0.0006 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
backlog
Capture single backlog items, or list and triage an existing project backlog. Use this skill whenever the user wants to file a bug, feature request, or backlog item without writing a full PRD, including casual requests mid-conversation like "create an issue for that", "add this to the backlog", or "file a quick bug…
add-community-extension
Add a community extension to the Spec Kit catalog from a GitHub issue submission. USE FOR: processing extension submission issues, validating catalog entries, updating catalog.community.json and docs/community/extensions.md, creating PRs. DO NOT USE FOR: creating new extensions from scratch, or first-party extension…
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
skill-cost-projections
Project remaining workflow cost from per-phase averages — warns on budget ceiling overruns.
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…
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.