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.
git 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/plugins/wecode-ai/wegent/wework-space)<a href="https://agentmods.dev/plugins/wecode-ai/wegent/wework-space"><img src="https://agentmods.dev/badge/plugins/wecode-ai/wegent/wework-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.
<a href="https://agentmods.dev/plugins/wecode-ai/wegent/wework-space"><img src="https://agentmods.dev/badge/plugins/wecode-ai/wegent/wework-space.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
wework-space 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 1mo 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.
What it actually says
{
"name": "wework-space",
"version": "0.2.2",
"description": "Provides project-space, Issue, attachment, and delivery tools to Wework Agent sessions."
}
What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 85 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 1mo ago Changed 392621a24e8a
- 1mo ago First seen · 6 lines scan A ccaff66e6c03
wework-space is a plugin published in the GitHub repository wecode-ai/Wegent (872 stars, last pushed today), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
aidd-pm
Product backlog artifacts, refinement, Product Briefs, Epics, User Stories, Tasks, Spikes, Defects, requirements, and specs.
aidd-vcs
External artifacts: repo-init, commit, pull-request, release-tag, issue-create, resolve-conflict.
aidd-orchestrator
Orchestrates the synchronous SDLC pipeline, async issue-to-PR automation, and the product backlog.
linearis
Agent skill for the linearis Linear.app CLI: preflight, discover-then-act usage protocol, JSON output, error envelopes and exit codes, ID resolution, discussions, files.
cloudformation-toolkit
CloudFormation infrastructure as code toolkit for stack design, template validation, and deployment strategies. Includes cfn architect agent for strategic CloudFormation architecture decisions.
asana
Asana project management integration. Connects Claude Code to Asana's V2 MCP server (https://mcp.asana.com/v2/mcp) to create and manage tasks, search projects, update assignments, and track progress. Requires a one-time setup of your own Asana OAuth app — run /asana-setup after installing.