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.
npx skills add porcupine-md/jonggrang --skill ssh-vps-deploymentgit clone --depth 1 https://github.com/porcupine-md/jonggrangWrote 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/skills/porcupine-md/jonggrang/ssh-vps-deployment)<a href="https://agentmods.dev/skills/porcupine-md/jonggrang/ssh-vps-deployment"><img src="https://agentmods.dev/badge/skills/porcupine-md/jonggrang/ssh-vps-deployment/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/skills/porcupine-md/jonggrang/ssh-vps-deployment"><img src="https://agentmods.dev/badge/skills/porcupine-md/jonggrang/ssh-vps-deployment.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00037 | $0.00902 |
| Opus 5 | $0.00018 | $0.00451 |
| Sonnet 5 | $0.00007 | $0.00180 |
| Haiku 4.5 | $0.00004 | $0.00090 |
Grade D, and why
ssh-vps-deployment scanned grade D with 3 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 9d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
3. Stop the existing application process (e.g., `pm2 stop {{project_name}}` or `sudo systemctl stop {{project_name}}`) to prevent file lock issues during deployment. Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
1. Ensure the SSH key is correctly configured (`~/.ssh/id_rsa` or another identity file). Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
4. Curl the application's public URL or local port to check for an HTTP 200 OK status. E.g., `curl -sSf http://<host>` or `ssh -i <key> <user>@<host> "curl -sSf http://localhost:<port>"`. How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
Deploying {{project_name}} ({{project_type}}) to a VPS via SSH. You will follow a strict 6-phase Deployment Lifecycle Contract.
Instructions
Execute the following phases in order:
Phase 1: Authentication
- Ensure the SSH key is correctly configured (
~/.ssh/id_rsaor another identity file). - For automated agents, ensure the SSH key string is written to a file, its permissions are restricted (
chmod 600), and it is used correctly with thessh -icommand. - Test connectivity by running
ssh -i <path-to-key> -o StrictHostKeyChecking=no <user>@<host> "echo Authentication successful". If this fails, abort the deployment.
Phase 2: Build
- Prepare the artifacts for deployment.
- If this is a Node.js or static frontend application, run
npm run buildoryarn buildlocally to generate thedist/orbuild/directory. - If this is a compiled language (Go, Rust), run the appropriate build command (e.g.,
go build -o app main.go) ensuring the target architecture matches the VPS (e.g.,GOOS=linux GOARCH=amd64).
Phase 3: Install / Provisioning
- Ensure the target directory structure exists on the VPS. For example:
ssh -i <key> <user>@<host> "mkdir -p /var/www/{{project_name}}". - Ensure necessary dependencies (e.g., Node.js, Python, PM2, Nginx) are installed on the server. Do not automatically install these unless explicitly required by the project configuration.
- Stop the existing application process (e.g.,
pm2 stop {{project_name}}orsudo systemctl stop {{project_name}}) to prevent file lock issues during deployment.
Phase 4: Deploy
- Ship the artifact to the VPS.
- Use
rsync(preferred for speed and reliability) orscpto copy the necessary files to the VPS. Example:rsync -avz -e "ssh -i <key> -o StrictHostKeyChecking=no" dist/ package.json <user>@<host>:/var/www/{{project_name}}/. - SSH into the VPS and install production dependencies if necessary:
ssh -i <key> <user>@<host> "cd /var/www/{{project_name}} && npm ci --production". - Start the application process. E.g.,
pm2 start {{project_name}}orsudo systemctl start {{project_name}}.
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.
- 9d ago First seen · 57 lines · 37 tokens per session scan D a66f09c19b1b
ssh-vps-deployment is a skill published in the GitHub repository porcupine-md/jonggrang (11 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 902 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it D with 3 findings (asks for root, reaches for credential files, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…