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 N-O-P-E/nope-marketplacenpx agentmods add plugins/n-o-p-e/nope-marketplace/gcp-setupgit clone --depth 1 https://github.com/N-O-P-E/nope-marketplaceWrote 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/n-o-p-e/nope-marketplace/gcp-setup)<a href="https://agentmods.dev/plugins/n-o-p-e/nope-marketplace/gcp-setup"><img src="https://agentmods.dev/badge/plugins/n-o-p-e/nope-marketplace/gcp-setup.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
gcp-setup 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 6d 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": "gcp-setup",
"description": "Automates Google Cloud Console setup via browser. Walks through project creation, API enabling, service accounts, IAM, billing, OAuth, Cloud Run, and firewall config — click by click. Auto-detects requirements from your codebase when invoked mid-feature.",
"version": "1.1.0",
"author": {
"name": "N-O-P-E"
},
"tags": ["browser-automation", "gcp", "google-cloud", "devops", "cloud-run"]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 161 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.
- 6d ago First seen · 10 lines scan A 382abbe51be3
gcp-setup is a plugin published in the GitHub repository N-O-P-E/nope-marketplace (8 stars, last pushed 4mo 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
devops-tools
DevOps automation: ClickHouse, Doppler, MLflow, Cloudflare Workers, pueue orchestration, notifications, session recovery, MiniMax consensus analysis.
homelab-ops
High-level operational runbooks for homelab management: DR-node power management, DNS ingress convergence, secrets-engine identity bring-up, Proxmox VE cluster operations, Terrakube operations, PXE netboot installs, LLM router operations, workstation off-box backup, Dell iDRAC BMC operations, and resumable ZFS…
infra-orchestration
Cross-repo infrastructure orchestration for Terraform and Ansible workflows.
infra-standards
Infrastructure standards for Proxmox, Terraform, Ansible: VMID/IP assignment ranges and the Terraform-to-Ansible inventory contract.
auto-scaling
Generate auto-scaling policies.
cdn-invalidation
Generate CDN cache invalidation strategies.