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/gosuda/portal-tunnelWrote 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/gosuda/portal-tunnel/portal-deploy)<a href="https://agentmods.dev/plugins/gosuda/portal-tunnel/portal-deploy"><img src="https://agentmods.dev/badge/plugins/gosuda/portal-tunnel/portal-deploy.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
portal-deploy 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 8d 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": "portal-deploy",
"version": "0.1.0",
"description": "Safely expose and verify local apps with Portal tunnels.",
"author": {
"name": "gosuda",
"url": "https://github.com/gosuda"
},
"homepage": "https://github.com/gosuda/portal-tunnel/tree/main/plugins/portal-deploy",
"repository": "https://github.com/gosuda/portal-tunnel",
"license": "MIT",
"keywords": ["portal", "tunnel", "deploy", "preview", "localhost", "expose"]
}
What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 215 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.
- 8d ago First seen · 14 lines scan A f59ced9f5c05
portal-deploy is a plugin published in the GitHub repository gosuda/portal-tunnel (266 stars, last pushed yesterday), 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-30.
Other plugins, from other repositories
bento
Install, deploy, update, and operate a bento VPS over SSH from Claude Code.
frontend-architect
Frontend stack expert for Cloudflare deployment, shadcn/ui components, and internal tools architecture. Guides technology choices, deployment patterns, and design system integration.
cybrix-deploy
Deploy the current static site to a live HTTPS URL via Cybrix. Detects Next.js export, Astro, Vite, Hugo, Eleventy, and plain HTML. Returns a live URL on .cbrx.cc in under 60 seconds.
spacelift
Procedural guide and references for working with Spacelift via the spacelift-local MCP - manage stacks, runs, policies, spaces, integrations, and the lifecycle of cloud resources through Intent (OpenTofu/Terraform).
axcient
Every x360Recover endpoint, plus the fleet-wide backup-health answers the API alone can't give — offline, joined, and agent-ready.
pocketnook
Deploy a GitHub repository or your working directory to a private URL, without leaving the agent that wrote it.