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-runtime)<a href="https://agentmods.dev/plugins/wecode-ai/wegent/wework-runtime"><img src="https://agentmods.dev/badge/plugins/wecode-ai/wegent/wework-runtime/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-runtime"><img src="https://agentmods.dev/badge/plugins/wecode-ai/wegent/wework-runtime.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
wework-runtime 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.
What it actually says
{
"name": "wework-runtime",
"version": "0.1.0",
"description": "Wework host workflows loaded on demand.",
"author": {
"name": "Wework"
},
"skills": "./skills/",
"interface": {
"displayName": "Wework Runtime",
"shortDescription": "Built-in Wework workflows"
}
}
What it installs
The manifest is a name and a version. 7 skills travel with it, and installing the plugin installs all of them — 153 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.
- 2d ago First seen · 14 lines scan A 30dff0e2a508
wework-runtime is a plugin published in the GitHub repository wecode-ai/Wegent (886 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-11-07.
wework-runtime compared with plugins from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| wework-runtimewecode-ai/Wegent | Plugin | 886 | today | Apache-2.0 | A | — | Claude Code |
| git-workflow-toolkitarmanzeroeight/fastagent-plugins | Plugin | 29 | 3mo ago | MIT | A | — | Claude Code |
| docker-toolkitarmanzeroeight/fastagent-plugins | Plugin | 29 | 3mo ago | MIT | A | — | Claude Code |
| python-toolkitarmanzeroeight/fastagent-plugins | Plugin | 29 | 3mo ago | MIT | A | — | Claude Code |
| api-toolkitarmanzeroeight/fastagent-plugins | Plugin | 29 | 3mo ago | MIT | A | — | Claude Code |
| aws-toolkitarmanzeroeight/fastagent-plugins | Plugin | 29 | 3mo ago | MIT | A | — | Claude Code |
| frontend-developerarmanzeroeight/fastagent-plugins | Plugin | 29 | 3mo ago | MIT | A | — | Claude Code |