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/wecode-ai/wegent/develop-wework-pluginnpx skills add wecode-ai/Wegent --skill develop-wework-plugingit clone --depth 1 https://github.com/wecode-ai/WegentWrote 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/wecode-ai/wegent/develop-wework-plugin)<a href="https://agentmods.dev/skills/wecode-ai/wegent/develop-wework-plugin"><img src="https://agentmods.dev/badge/skills/wecode-ai/wegent/develop-wework-plugin.svg" alt="Measured on agentmods" height="20"></a>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.00064 | $0.02870 |
| Opus 5 | $0.00032 | $0.01435 |
| Sonnet 5 | $0.00013 | $0.00574 |
| Haiku 4.5 | $0.00006 | $0.00287 |
Grade A, and why
develop-wework-plugin 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 today.
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 — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Develop a Wework plugin
Treat the Wework package as the outer delivery unit. It may declare a nested
Codex plugin through wework.codexPlugin; the Codex plugin must never own or
gate the Wework plugin.
Use the bundled development kit
This Skill includes the complete public Wework extension catalog, one exhaustive smoke-test plugin, three focused API references, and three product-oriented showcase plugins:
- Read references/extension-points.md before choosing a UI surface. It documents descriptor fields, component props, and the browser-module boundary.
- Inspect assets/ui-extension-demo before writing a low-level UI contribution.
- Inspect assets/reference-plugins for runnable, independently installable examples of Composer augmentation, persistent workflow UI, and typed desktop-host integration. Copy only the closest example into the user's writable project, then delete every contribution the plugin does not need.
- Start with assets/showcase-plugins when the user wants a product-quality example. Workspace Copilot, Test Explorer, and Dev Environments represent popular AI-assistant, testing, and development-environment categories with deliberately different interaction models.
- Never edit files inside an installed plugin cache. Resolve these resources relative to this Skill, and copy examples to the active project first.
The catalog covers all public host slots:
- Navigation and apps:
wework.action,wework.app,wework.route,wework.sidebar.navigation, andwework.settings.page. - Project and workspace:
wework.plugins.action,wework.project.create.section,wework.project.work.section,wework.workspace.menu.section,wework.workspace.tab,wework.workspace.sidebar.tab,wework.workspace.toolbar.action,wework.workspace.bottom-panel.tab, andwework.runtime-profile.workspace-policy. - Composer:
wework.composer.action. - Context:
wework.task.status,wework.environment.section, andwework.board.card.status. - Shell:
wework.shell.before,wework.shell.after, andwework.shell.overlay.
What ships with it
42 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.
- assets/reference-plugins/endpoint-watch-demo/client.js 19 KB runs code
- assets/reference-plugins/endpoint-watch-demo/cordis.patch.yml 86 B
- assets/reference-plugins/endpoint-watch-demo/index.js 69 B runs code
- assets/reference-plugins/endpoint-watch-demo/package.json 778 B
- assets/reference-plugins/endpoint-watch-demo/README.md 557 B
- assets/reference-plugins/focus-board-demo/client.js 15 KB runs code
- assets/reference-plugins/focus-board-demo/cordis.patch.yml 80 B
- assets/reference-plugins/focus-board-demo/index.js 66 B runs code
- assets/reference-plugins/focus-board-demo/package.json 772 B
- assets/reference-plugins/focus-board-demo/README.md 409 B
- assets/reference-plugins/prompt-library-demo/client.js 12 KB runs code
- assets/reference-plugins/prompt-library-demo/cordis.patch.yml 86 B
- assets/reference-plugins/prompt-library-demo/index.js 69 B runs code
- assets/reference-plugins/prompt-library-demo/package.json 785 B
- assets/reference-plugins/prompt-library-demo/README.md 464 B
- assets/reference-plugins/README.md 552 B
- assets/reference-plugins/reference-plugins.test.mjs 6.9 KB runs code
- assets/showcase-plugins/quality-guardian-demo/client.js 9.7 KB runs code
- assets/showcase-plugins/quality-guardian-demo/cordis.patch.yml 128 B
- assets/showcase-plugins/quality-guardian-demo/index.js 6.2 KB runs code
- assets/showcase-plugins/quality-guardian-demo/package.json 791 B
- assets/showcase-plugins/quality-guardian-demo/README.md 555 B
- assets/showcase-plugins/README.md 916 B
- assets/showcase-plugins/runtime-doctor-demo/client.js 13 KB runs code
- assets/showcase-plugins/runtime-doctor-demo/cordis.patch.yml 134 B
- assets/showcase-plugins/runtime-doctor-demo/index.js 4.4 KB runs code
- assets/showcase-plugins/runtime-doctor-demo/package.json 803 B
- assets/showcase-plugins/runtime-doctor-demo/README.md 710 B
- assets/showcase-plugins/showcase-plugins.test.mjs 8.7 KB runs code
- assets/showcase-plugins/workspace-copilot-demo/client.js 12 KB runs code
- assets/showcase-plugins/workspace-copilot-demo/cordis.patch.yml 136 B
- assets/showcase-plugins/workspace-copilot-demo/index.js 4.4 KB runs code
- assets/showcase-plugins/workspace-copilot-demo/package.json 790 B
- assets/showcase-plugins/workspace-copilot-demo/README.md 672 B
- assets/ui-extension-demo/client.js 15 KB runs code
- assets/ui-extension-demo/client.test.mjs 7.7 KB runs code
- assets/ui-extension-demo/cordis.patch.yml 90 B
- assets/ui-extension-demo/index.js 71 B runs code
- assets/ui-extension-demo/package.json 836 B
- assets/ui-extension-demo/README.en.md 1.7 KB
- assets/ui-extension-demo/README.md 1.6 KB
- references/extension-points.md 20 KB
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.
- today Changed · +53 lines 271041ce79fe
- 2d ago First seen · 233 lines · 64 tokens per session scan A c581a3c86135
develop-wework-plugin is a skill published in the GitHub repository wecode-ai/Wegent (782 stars, last pushed today), licensed Apache-2.0. It adds 64 tokens to every session and 2,870 once invoked, about $0.0003 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-03.
Other skills, from other repositories
contribute-to-eliza
Finish and prove a scoped elizaOS GitHub issue, or independently review and repair an open elizaOS pull request. Use when contributing compute to elizaOS by selecting unclaimed work, implementing or reviewing changes, adding real tests and evidence, validating artifacts, or preparing a contribution for maintainer…
eliza-cloud
Use when the task involves Eliza Cloud or elizaOS Cloud as a managed backend, app platform, deployment target, billing layer, or monetization surface. The catch-all skill for any user request about THEIR existing apps / containers / earnings / credits / api-keys / analytics / billing / payment requests / payouts …
build-monetized-app
Use when the task is building a new app on Eliza Cloud that earns money — chat apps, agent apps, MCP-backed tools, anything that calls the cloud's chat/messages/inference endpoints on behalf of users. Covers app registration, container deploy, markup configuration, affiliate header, app charge requests, x402 payment…
discord
Use when you need to control Discord from Otto via the discord tool: send messages, react, post or upload stickers, upload emojis, run polls, manage threads/pins/search, create/edit/delete channels and categories, fetch permissions or member/role/channel info, set bot presence/activity, or handle moderation actions in…
eliza-cloud-buy-domain
Use whenever a user wants to register or buy a custom domain for an Eliza Cloud app — including in the same request as building the app ("build me X and put it on Y.com"). Uses Cloudflare as registrar after explicit user confirmation, paid from the user's existing cloud credit balance. Pairs with build-monetized-app…
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.