What is wework-notifications?

A notification tool for sending persistent in-app messages through Wework, with attempted delivery to the recipient’s connected messaging sessions. Wework is a workplace collaboration service.

Use it to send alerts, greetings, or automation updates to yourself or another permitted project member, optionally linking to a board or other destination.

It avoids requiring a project or board just to send a notification, while allowing a message to include a destination link and optional project context.

wework-notifications — Skill for Claude Code and Codex by wecode-ai

Install

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.

Any agent

npx skills add wecode-ai/Wegent --skill wework-notifications

Clone the repo

git clone --depth 1 https://github.com/wecode-ai/Wegent

Made for: Claude Code, Codex.

Or install wework-space, the plugin that ships this one along with the rest of its 2 skills.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/wecode-ai/wegent/wework-notifications/github.svg)](https://agentmods.dev/skills/wecode-ai/wegent/wework-notifications)

Your own site

<a href="https://agentmods.dev/skills/wecode-ai/wegent/wework-notifications"><img src="https://agentmods.dev/badge/skills/wecode-ai/wegent/wework-notifications/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/wecode-ai/wegent/wework-notifications"><img src="https://agentmods.dev/badge/skills/wecode-ai/wegent/wework-notifications.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 508 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00046	$0.00508
Opus 5	$0.00023	$0.00254
Sonnet 5	$0.00009	$0.00102
Haiku 4.5	$0.00005	$0.00051

Measured 2d ago against content hash 086531064df4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

wework-notifications 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.

wework/resources/bundled-plugins/wework-personal/plugins/wework-space/skills/wework-notifications/SKILL.md · 17 lines

What it actually says

Wework notifications

Use wework_space.send_notification to create a persistent user notification. It also attempts delivery to the recipient's connected IM sessions. An authenticated Backend connection is required; a project or board is not required to notify yourself.

For an ordinary request such as “给我发个通知，说你好”, call send_notification with a concise title and body: "你好". Do not require a project, create a board, or search for an Issue first.
space_id and item_id are optional source context. Backend project conversations can use their bound context; ordinary and local-project conversations can send without it. Supply source IDs only when the notification relates to that accessible Backend project or Issue.
For “notify me”, omit recipient_user_id; the tool uses the authenticated user. For another recipient, resolve their ID through get_assignment_candidates and use a member of the same project.
Supply a concise title and body describing what happened and any requested action. Use optional url for the requested click destination independently of source context. For “给我发个你好的通知，然后点击打开看板页面”, send title: "你好", body: "你好", url: "wework://boards". The page opens only when the notification is clicked; do not call browser open as a substitute. Other supported destinations are wework://boards/{projectId}, wework://boards/{projectId}/issues/{encodedItemId}, and wework://tasks/{encodedDeviceId}/{encodedTaskId}; use known identifiers and URL-encode each segment. Without url, a source link is generated if supplied; otherwise the notification has no click destination.
An automation instruction such as “if the review fails, notify me in Wework” authorizes sending when that condition occurs. Do not send unrelated notifications.
Assigning a board Issue to a different human automatically creates a notification by default. Do not send a second notification for the same assignment. Honor an explicit request not to notify.
Report success only when the tool returns a saved notification. On an error, report it; do not substitute shell commands or external IM tools.

Changes

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 · 17 lines · 46 tokens per session scan A 086531064df4

Subscribe to this mod's changes

wework-notifications is a skill published in the GitHub repository wecode-ai/Wegent (848 stars, last pushed today), licensed Apache-2.0. It adds 46 tokens to every session and 508 once invoked, about $0.0002 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-09-09.

Claude Code Productivity Project management agent ai chatbot codex wework

things-mac

Manage Things 3 via the things CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks Otto to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.

elizaOS/eliza · 67 tokens

notion

Notion API for creating and managing pages, databases, and blocks. Use when the user wants to create a Notion page, query a Notion database, update Notion properties, search Notion, add content to Notion, manage Notion blocks, or interact with Notion data sources and workspaces via the API.

elizaOS/eliza · 69 tokens

tmux

Remote-control tmux sessions for interactive CLIs by sending keystrokes, capturing pane output, and managing terminal multiplexer windows. Enables parallel coding-agent orchestration, background process management, and REPL interaction via sockets. Use when the agent needs to launch, monitor, or coordinate…

elizaOS/eliza · 87 tokens

slack

Use when the agent needs to send, edit, delete, or read Slack messages, add or list emoji reactions, pin or unpin messages, fetch member info, or list custom emoji in Slack channels and DMs. Handles all Slack workspace interactions including message management, reaction workflows, pinned-item management, and user…

elizaOS/eliza · 73 tokens

trello

Manages Trello boards, lists, and cards via the Trello REST API. Use when the user wants to create cards, move tasks between lists, list boards, add comments, archive cards, or check what is on a Trello board. Handles authentication, pagination, and rate-limit awareness for all Trello REST endpoints.