wework-project-space

wework-project-space is a skill for Claude Code from wecode-ai/Wegent. It costs 39 tokens per session (433 once invoked), scanned A, original, Apache-2.0.

A set of instructions for working with a Wework project space, including its current Issue, files, deliveries, members, and board items. Wework is the surrounding project-management system.

In plain words
What is it for?
Use it to inspect or update the active Wework project, read Issue details and attachments, and work with deliveries, members, or board items.
Why use it?
It explains which project information to read and in what order when an Issue is active, reducing the risk of using the wrong project or missing attached files.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the wework-space plugin — 2 skills shipped together

Good fit Use it to inspect or update the active Wework project, read Issue details and attachments, and work with deliveries, members, or board items.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/wecode-ai/wegent/wework-project-space
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-project-space
Clone the repo
git clone --depth 1 https://github.com/wecode-ai/Wegent

Made for: Claude Code.

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.

agentmods badge for wework-project-space

README.md
[![agentmods](https://agentmods.dev/badge/skills/wecode-ai/wegent/wework-project-space/github.svg)](https://agentmods.dev/skills/wecode-ai/wegent/wework-project-space)
Your own site
<a href="https://agentmods.dev/skills/wecode-ai/wegent/wework-project-space"><img src="https://agentmods.dev/badge/skills/wecode-ai/wegent/wework-project-space/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.

agentmods 80×15 button for wework-project-space

Your own site · 80×15
<a href="https://agentmods.dev/skills/wecode-ai/wegent/wework-project-space"><img src="https://agentmods.dev/badge/skills/wecode-ai/wegent/wework-project-space.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 433 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00039 $0.00433
Opus 5.5 $0.00016 $0.00173
Sonnet 5.5 $0.00008 $0.00087
Haiku 4.5 $0.00004 $0.00043

Measured 3d ago against content hash e162b4c23588, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

wework-project-space scanned grade A with 1 finding 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 3d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

5. Do not probe MCP resources, use Shell or `curl`, scrape the browser, or parse `wegent://` attachment URLs.
wework/resources/bundled-plugins/wework-personal/plugins/wework-space/skills/wework-project-space/SKILL.md · 22 lines

What it actually says

Wework project space

Use the wework_space MCP tools for project-space work.

  1. Call get_current_context before answering questions about the current Issue.
  2. Call get_board_item with that context before interpreting the Issue description. Read list_board_item_comments as well for PR links, follow-up requirements and review feedback. It returns the latest 200 comments by default; use limit (up to 500) and after_sequence to page forward. Write with add_board_item_comment to the same visible Issue activity.
  3. Use list_item_attachments and read_item_attachment to inspect Issue attachments.
  4. Use the current context instead of asking the user to repeat a project or Issue identifier.
  5. Do not probe MCP resources, use Shell or curl, scrape the browser, or parse wegent:// attachment URLs.
  6. Never substitute Git or provider APIs when wework_space reports an offline, authorization, or capability error.
  7. Do not claim Issue content is unavailable until the matching wework_space call returns an error.

Human assignee changes notify the new owner by default. Do not send a duplicate notification. For user-requested alerts or automation conditions, use send_notification; omit recipient_user_id to notify the authenticated user.

To @ a member in a shared Backend project's comment, resolve the member with get_assignment_candidates, then pass mentions=[{"type":"user","id":"52","label":"qindi"}] together with the comment body, space_id and item_id to add_board_item_comment. Plain @name text does not notify. This uses the same member and Issue access checks as the page and creates one notification per recipient; do not also call send_notification. Pure local projects do not have a shared member inbox.

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.

  1. 3d ago Changed · +2 lines e162b4c23588
  2. 6d ago Changed · +1 lines 45679e67bfd8
  3. 1mo ago Changed · +2 lines ce559734436f
  4. 1mo ago First seen · 17 lines · 39 tokens per session scan A 8bb37805715f

Subscribe to this mod's changes

wework-project-space is a skill published in the GitHub repository wecode-ai/Wegent (878 stars, last pushed today), licensed Apache-2.0. It adds 39 tokens to every session and 433 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.