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 jpantsjoha/googlecloud-pluginnpx agentmods add plugins/jpantsjoha/googlecloud-plugin/marketplacegit clone --depth 1 https://github.com/jpantsjoha/googlecloud-pluginGrade A, and why
googlecloud-plugin-marketplace 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 yesterday.
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": "googlecloud-plugin-marketplace",
"description": "A full Google Cloud delivery team for coding agents — design-first, security-first, Well-Architected, with agentic (ADK / A2A / AP2 / MCP) coverage.",
"owner": {
"name": "Jaroslav Pantsjoha",
"url": "https://uk.linkedin.com/in/johas"
},
"plugins": [
{
"name": "googlecloud-plugin",
"description": "A full Google Cloud delivery team for your coding agent: solution designer, GCP architect, agent architect, security, SRE, and QA — wired into a design-first, security-first delivery gate, with eleven service skills and MCP server setup.",
"version": "0.2.0",
"source": "./",
"author": {
"name": "Jaroslav Pantsjoha",
"url": "https://uk.linkedin.com/in/johas"
}
}
]
}
What ships with it
1 file beside marketplace.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.
- yesterday First seen · 21 lines scan A 72fa302cb6cb
googlecloud-plugin-marketplace is a plugin published in the GitHub repository jpantsjoha/googlecloud-plugin (4 stars, last pushed 24d 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
avoid-ai-writing
Audit and rewrite prose that reads as machine-generated, across READMEs, changelogs, PR descriptions, docs, and blog copy, with detect-only, rewrite, and edit-in-place modes.
accessibility-compliance
WCAG accessibility auditing, compliance validation, UI testing for screen readers, keyboard navigation, and inclusive design.
agent-orchestration
Multi-agent system optimization, agent improvement workflows, and context management.
agent-teams
Orchestrate multi-agent teams for parallel code review, hypothesis-driven debugging, and coordinated feature development using Claude Code's Agent Teams.
api-scaffolding
REST and GraphQL API scaffolding, framework selection, backend architecture, and API generation.
application-performance
Application profiling, performance optimization, and observability for frontend and backend systems.