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-managegit 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-manage)<a href="https://agentmods.dev/skills/renuo/deploio-claude-plugin/deploio-manage"><img src="https://agentmods.dev/badge/skills/renuo/deploio-claude-plugin/deploio-manage/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/renuo/deploio-claude-plugin/deploio-manage"><img src="https://agentmods.dev/badge/skills/renuo/deploio-claude-plugin/deploio-manage.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.00000 | $0.05663 |
| Opus 5.5 | $0.00000 | $0.02265 |
| Sonnet 5.5 | $0.00000 | $0.01133 |
| Haiku 4.5 | $0.00000 | $0.00566 |
Grade A, and why
deploio-manage scanned grade A 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 2mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
> - Retrieve the user's current IP: `curl -s https://api.ipify.org` How it starts
The opening of the file, as written. The whole thing — 573 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploio: Managing a Running App
Your role is coordinator. You never run commands yourself — you spawn deploio-cli agents with mode: bypassPermissions for all execution. Identify the operation, inspect current state if needed, confirm impactful changes, then execute.
Communication style: Speak to the user in plain language — describe what you'll do, never show raw nctl commands. Say "I'll add the Sidekiq worker to your app" not "I'll run nctl update app ... --worker-job-name=sidekiq". Agents manage the CLI entirely on the user's behalf.
Phase 0: Identify operation from context
Autoinfer app and project before asking. Run:
git remote get-url origin # https://github.com/acme/myapp → repo name only (not the org)
nctl auth whoami # → active organization (marked with *)
git branch --show-current # main → app=main
Derive: app = <branch> (e.g. main), org from the *-marked entry in nctl auth whoami (not the git URL), project = <org>-<repo> (e.g. renuotest-myapp — never just <repo>; nctl errors).
State your inference inline: "Using app main in project renuotest-myapp (org renuotest) — let me know if that's different." Proceed immediately. Only ask explicitly if there is no git remote configured, or if a subsequent nctl command fails because the organization doesn't exist.
From the conversation, also determine:
- Operation — from the table below
| User says | Operation | Go to |
|---|---|---|
| "show logs", "tail logs", "what do the logs say" | logs-app |
→ Logs |
| "build logs", "watch the build" | logs-build |
→ Logs |
| "rails console", "rails c", "open a shell", "run a command", "exec", "rake task" | exec |
→ Exec |
| "list apps", "what apps do I have", "check status", "is it running", "resource usage" | inspect |
→ Inspect |
| "basic auth credentials", "get the password" | basic-auth-credentials |
→ Inspect |
| "deploy new version", "change branch", "redeploy" | git-revision |
→ Execute |
| "retry build", "force rebuild" | retry-build |
→ Execute |
| "re-deploy", "retry release" | retry-release |
→ Execute |
| "add / change env var" | env |
→ Execute |
| "change build env", "change Ruby version", "change Node version" | build-env |
→ Execute |
| "scale", "more replicas" | replicas |
→ Execute |
| "upsize", "change size" | size |
→ Execute |
| "custom domain", "add host" | hosts |
→ Execute |
| "health check", "health probe" | health-probe |
→ Execute |
| "enable basic auth", "disable basic auth" | basic-auth |
→ Execute |
| "add worker", "Sidekiq", "good_job" | worker-job |
→ Execute |
| "remove worker", "delete worker" | delete-worker-job |
→ Execute |
| "add scheduled job", "add cron", "scheduled task" | scheduled-job |
→ Execute |
| "remove scheduled job", "remove cron" | delete-scheduled-job |
→ Execute |
| "run migrations on deploy", "deploy job" | deploy-job |
→ Execute |
| "disable deploy job", "remove deploy job" | delete-deploy-job |
→ Execute |
| "move repo", "change git URL" | git-url |
→ Execute |
| "rollback", "previous version", "revert deploy", "go back to last working" | rollback |
→ Execute |
| "restart app", "restart the app" | restart |
→ Execute |
| "pause app", "stop billing", "hibernate" | pause |
→ Execute |
| "resume app", "unpause", "start app" | resume |
→ Execute |
| "copy app", "duplicate app", "clone app" | copy |
→ Execute |
What ships with it
1 file 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.
- 2mo ago First seen · 573 lines · 0 tokens per session scan A 3bfc0a91fec1
deploio-manage is a skill published in the GitHub repository renuo/deploio-claude-plugin (3 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,663 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
render
Use when deploying or fixing an app on Render — web services, background workers, cron jobs, private services, managed Postgres and Key-Value, and especially the render.yaml Blueprint. Covers deploys that fail with no open ports detected, 502s on first deploy, free-tier cold starts, and a free Postgres about to expire…
relay-deploy
Set up a complete deployment configuration — Dockerfile, deployment manifest, environment config, and rollback procedure. Use when asked about "deployment setup", "how do I deploy this", "deployment strategy", or "rollback plan".
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…
blockchain-infrastructure
Use this skill when asked about blockchain node deployment, RPC infrastructure, CI/CD for smart contracts, monitoring and alerting for blockchain networks, MEV infrastructure (Flashbots, builders, relays), key management (KMS, HSM), and environment management for devnet/testnet/staging/mainnet. Languages: Go, Rust…
deploy
Deploy application to staging or production environments.
deployment
Deploy applications to DigitalOcean App Platform via GitHub Actions with proper environment management and secrets handling. Use when setting up CI/CD pipelines, configuring staging/production environments, managing deployment secrets, or creating GitHub Actions workflows.