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.
/plugin marketplace add cloudshipai/stationnpx agentmods add plugins/cloudshipai/station/marketplacegit clone --depth 1 https://github.com/cloudshipai/stationGrade A, and why
cloudshipai-station 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": "cloudshipai-station",
"owner": {
"name": "CloudShip AI",
"email": "[email protected]"
},
"metadata": {
"description": "Station AI agent orchestration platform plugins",
"version": "1.0.0"
},
"plugins": [
{
"name": "station",
"source": "./claude-code-plugin",
"description": "Lightweight Station integration with skills and slash commands - guides Claude through Station operations",
"version": "1.0.0",
"author": {
"name": "CloudShip AI"
},
"homepage": "https://docs.cloudshipai.com/station/overview",
"repository": "https://github.com/cloudshipai/station",
"license": "Apache-2.0",
"keywords": ["station", "agents", "mcp", "orchestration", "ai", "cloudship", "sre", "devops", "skills"]
},
{
"name": "station-agent",
"source": "./claude-code-plugin-agent",
"description": "Full Station integration with pre-configured subagent - autonomous Station operations via dedicated expert agent",
"version": "1.0.0",
"author": {
"name": "CloudShip AI"
},
"homepage": "https://docs.cloudshipai.com/station/overview",
"repository": "https://github.com/cloudshipai/station",
"license": "Apache-2.0",
"keywords": ["station", "agents", "mcp", "orchestration", "ai", "cloudship", "sre", "devops", "subagent"]
}
]
}
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 · 40 lines scan A b5d831bc1e79
cloudshipai-station is a plugin published in the GitHub repository cloudshipai/station (429 stars, last pushed 7mo ago), 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
jwx-dev-v4
Guide for developing Go applications with github.com/lestrrat-go/jwx v4 — parse and sign JWTs, work with JWS/JWE/JWK, pick algorithms, and avoid common footguns.
jenkins-cli
GitHub CLI-style interface for Jenkins controllers - create multibranch jobs, inspect config.xml, and manage runs, logs, artifacts, credentials, nodes, and queues.
hn-cli
Plugin marketplace listing 1 plugin: hn.
callee
Plugin marketplace listing 1 plugin: callee.
capacitor-plugin-dev
Capacitor plugin development skills — create, upgrade, and add SPM support to plugins.
goalkeeper
Durable goal-following for Claude Code: contracts with definition-of-done, subagent judge gates, executor-subagent chain execution, and adaptive missions — with all state mechanics executed by a tested CLI and invariants enforced by hooks. Inspired by OpenAI Codex /goal and the Ralph loop pattern.