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/Cyberdyne-OS/cyberdyne-mcpWrote 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/cyberdyne-os/cyberdyne-mcp/cyberdyne-mcp)<a href="https://agentmods.dev/plugins/cyberdyne-os/cyberdyne-mcp/cyberdyne-mcp"><img src="https://agentmods.dev/badge/plugins/cyberdyne-os/cyberdyne-mcp/cyberdyne-mcp/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/cyberdyne-os/cyberdyne-mcp/cyberdyne-mcp"><img src="https://agentmods.dev/badge/plugins/cyberdyne-os/cyberdyne-mcp/cyberdyne-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
cyberdyne 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 11d 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": "cyberdyne",
"description": "The engagement marketplace for the agent economy — AI agents and communities fund quests (follows, reposts, replies, quotes, original posts); verified-X humans complete them, paid per approved action from a non-custodial x402 escrow on Base. Also ground-truthing, capture, agent evals, demos, and expert review. Bundles the CYBERDYNE MCP gateway + a usage skill.",
"version": "0.7.3",
"author": {
"name": "Cyberdyne-OS",
"email": "[email protected]"
},
"homepage": "https://cyberdyne-os.xyz",
"repository": "https://github.com/Cyberdyne-OS/cyberdyne-mcp",
"keywords": [
"mcp",
"ai-agents",
"agent-marketplace",
"human-in-the-loop",
"agentic-payments",
"get-paid-by-ai"
],
"mcpServers": {
"cyberdyne": {
"command": "npx",
"args": ["-y", "cyberdyne-mcp"],
"env": {
"CYBERDYNE_IDENTITY_TOKEN": "${CYBERDYNE_IDENTITY_TOKEN}"
}
}
}
}
What it installs
The manifest is a name and a version. 1 skill, 1 MCP server travel with it, and installing the plugin installs all of them — 191 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json 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.
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.
- 11d ago First seen · 29 lines scan A 6d916f55ea58
cyberdyne is a plugin published in the GitHub repository Cyberdyne-OS/cyberdyne-mcp (1 stars, last pushed 2mo ago), licensed MIT. 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-31.
Other plugins, from other repositories
security
Threat modeling, security architecture review, incident response, vulnerability management, and access and identity. Reviewer-class: blocking findings are not overrulable by the department under review.
data-analytics
Data governance, warehouse and semantic modeling, business intelligence, and AI/ML governance.
executive
Direction, capital and attention allocation, cross-functional arbitration, strategy validation, and the method for structuring the organization itself.
revenue
Outbound, sales enablement, revenue operations, pricing and packaging, activation, retention, and referrals.
e2a
Open-source email API for applications and AI agents — transactional sending from any product, per-agent two-way inboxes, structured SPF/DKIM/DMARC evidence, and a queryable event log. 78 MCP tools over hosted streamable HTTP with OAuth.
selat
Discover and call paid AI capabilities via a two-tier loop — vetted multi-step skills first, then a federated x402 / MPP endpoint catalog (image/video/audio generation, translation, web scraping, data enrichment, real-time data, on-chain actions). Payments settle from your own Circle Agent Wallet (MPC self-custody …