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 renuo/deploio-claude-plugin --skill deploio-deploygit clone --depth 1 https://github.com/renuo/deploio-claude-pluginWrote 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/renuo/deploio-claude-plugin/deploio-deploy)<a href="https://agentmods.dev/skills/renuo/deploio-claude-plugin/deploio-deploy"><img src="https://agentmods.dev/badge/skills/renuo/deploio-claude-plugin/deploio-deploy.svg" alt="Measured on agentmods" 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.00163 | $0.05259 |
| Opus 5 | $0.00081 | $0.02629 |
| Sonnet 5 | $0.00033 | $0.01052 |
| Haiku 4.5 | $0.00016 | $0.00526 |
Grade C, and why
deploio-deploy scanned grade C with 1 finding 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.
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.
- Ask the user for the path to their deploy key, or offer to use `~/.ssh/id_ed25519` How it starts
The opening of the file, as written. The whole thing — 441 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploio: First-Time App Deployment
Your role is coordinator. You never run commands yourself — you spawn deploio-cli agents for all execution. Gather context via an agent, resolve blockers, confirm the plan with the user, then spawn an executor and a monitor agent in parallel.
Communication style: Speak to the user in plain language — describe what will happen, never show raw nctl commands in your responses to the user. Agents manage the CLI entirely on the user's behalf. Keep tone calm and direct — avoid exclamations and over-eager phrases like "Great news!" or "Awesome!".
Phase 0: Pre-flight check (from conversation context only — no commands)
Before spawning any agent, evaluate these four conditions from what the user has already told you:
| Condition | Known if… |
|---|---|
nctl_known |
User mentioned installing nctl, or ran it in this session |
remote_known |
A git URL is visible in the conversation |
auth_known |
User mentioned a Deploio project name or logged in |
framework_known |
User said "Rails app", "Next.js", etc. |
If remote_known is false, run git remote get-url origin and git branch --show-current to discover the URL and branch. If a remote is found, derive app = <branch> (e.g. main), org from nctl auth whoami (the *-marked one — not the git URL), and project = <org>-<repo> (e.g. renuotest-myapp — never just <repo>; nctl errors). State: "I'll deploy project renuotest-myapp, app main, in organization renuotest — let me know if that's different." Only ask for a URL from scratch if no remote is configured.
Pass any known values into the gather-context spec as hints to speed up detection.
Phase 1: Gather context
Spawn the deploio-cli agent with mode: bypassPermissions and this spec:
task: gather-context
hints:
remote_url: <from context, or null>
framework: <from context, or null>
nctl_installed: <from context, or null>
What the agent must do
Constraints: Do not run any nctl commands during context gathering — nctl commands may require auth and will produce misleading errors before the project exists. Use only: git commands, file system reads, and nctl version.
What ships with it
6 files beside SKILL.md 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.
- 8d ago First seen · 441 lines · 0 tokens per session scan C a06ffea7f7e0
deploio-deploy is a skill published in the GitHub repository renuo/deploio-claude-plugin (3 stars, last pushed 2mo ago), licensed MIT. It adds 163 tokens to every session and 5,259 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it C with 1 finding (reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
development-workflow
Orchestrates the complete Falcon Foundry app lifecycle from requirements through deployment. TRIGGER when user asks to "create a Foundry app", "build a Foundry app", "plan a Foundry app", runs any foundry apps CLI command, or discusses Foundry app architecture. DO NOT TRIGGER when user is working on a specific…
cloud-run-basics
Cloud Run expert guidance. Use when deploying services, running jobs, or managing worker pools for HTTP, scheduled tasks, or background processing.
deploy-render
Deploy to Render using render.yaml (Infrastructure as Code) or the Render dashboard. Handles web services, background workers, cron jobs, and static sites.
deploy-vercel
Deploy a project to Vercel using the Vercel CLI. Handles first-time setup, preview deploys, production deploys, environment variables, custom domains, and build failure troubleshooting.
deploy-railway
Deploy to Railway using the Railway CLI. Handles project setup, deployments, environment variables, and service configuration.
deploy-rollback
Roll back a deployment to the previous version on Vercel, Railway, or Fly.io. Always checks for database migration safety before rolling back.