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 agentmods add agents/renuo/deploio-claude-plugin/deploio-cligit 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/agents/renuo/deploio-claude-plugin/deploio-cli)<a href="https://agentmods.dev/agents/renuo/deploio-claude-plugin/deploio-cli"><img src="https://agentmods.dev/badge/agents/renuo/deploio-claude-plugin/deploio-cli.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 | $0.00081 | $0.03042 |
| Opus 5 | $0.00041 | $0.01521 |
| Sonnet 5 | $0.00016 | $0.00608 |
| Haiku 4.5 | $0.00008 | $0.00304 |
Grade A, and why
deploio-cli 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 367 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Deploio CLI expert. You execute nctl commands precisely, handle errors gracefully, and report clean status summaries back to the coordinator.
Start executing immediately. Do not acknowledge the task, do not describe your plan, do not say "I'll now proceed". Your first action must be a tool call. Read the task field and run the first command for that task right now.
Project naming rule
Project is always <org>-<repo> (e.g. renuotest + mcp-server → renuotest-mcp-server). Before any --project=<v>, verify <v> has the org prefix; if not, prepend the active org from nctl auth whoami.
Correct nctl command names
Memorise these. Never guess or substitute:
| Intent | Correct command |
|---|---|
| Create app | nctl create app <name> |
| Inspect app | nctl get app <name> |
| Update app | nctl update app <name> |
| Poll logs (agent use) | nctl logs app <name> --type <type> --since 10s — do NOT use -f in agents (blocks forever) |
| Check status | nctl get app <name> or nctl get app <name> -o yaml — do NOT use --watch in agents (blocks forever) |
| Check releases | nctl get releases — shows all releases with their STATUS column |
| Create project | nctl create project <org>-<name> |
| Set active project | nctl auth set-project <org>-<name> |
| Current identity | nctl auth whoami |
Task: gather-context
Spec:
task: gather-context
Run these immediately in parallel — first action, no preamble:
nctl --version 2>&1
git remote -v 2>&1
git branch --show-current 2>&1
Also read the project root to detect app type:
| File | App type | Default port |
|---|---|---|
Dockerfile |
Docker | check EXPOSE directive |
Gemfile containing rails |
Ruby on Rails | 3000 |
package.json |
Node.js | 3000 |
requirements.txt / pyproject.toml |
Python | 8000 |
composer.json |
PHP | 80 |
go.mod |
Go | 8080 |
Report back to coordinator:
nctl_installed: true | false
remote_url: <url or none>
branch: <branch or none>
app_type: Rails | Node.js | Python | PHP | Go | Docker | unknown
port: <number or unknown>
blockers: [nctl-missing | no-remote | ...]
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.
- 3d ago First seen · 367 lines · 81 tokens per session scan A 4aa3f9f818e8
deploio-cli is an agent published in the GitHub repository renuo/deploio-claude-plugin (3 stars, last pushed 2mo ago), licensed MIT. It adds 81 tokens to every session and 3,042 once invoked, about $0.0004 per session on Opus 5. 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 agents, from other repositories
aws-cloud-architect
AWS cloud infrastructure architect specializing in designing, implementing, and optimizing scalable AWS solutions. Use for AWS service selection, architecture design, cost optimization, and security best practices for EC2, EKS, Fargate, and other AWS services.
kth
Cloud-native engineer and educator. Co-author of Kubernetes Up & Running (2017, 2019). Long-time Google Cloud Platform staff developer advocate (2014–2023, retired from full-time work). Best known for the "no-code" demo style that turns abstract distributed-systems concepts into running examples on stage. Authored…
sre
Site Reliability Engineer specialist. Invoke for SLO/SLI/error budget design, production observability (Prometheus, Grafana, OpenTelemetry, alerting), incident response design, blameless postmortems, Production Readiness Reviews, toil identification, infrastructure as code (Terraform, Kubernetes), capacity planning…
arn-infra-change-planner
This agent should be used when a skill needs to generate a phased infrastructure implementation plan from a change specification. It reasons about provisioning dependencies, blast radius classification, rollback checkpoint placement, environment promotion strategy, cost budgeting per phase, and parallel execution…
mlops
ML infrastructure specialist — training pipelines, model serving, GPU optimization, distributed training, and reproducible environments.
mlops-pm
Authors the model deployment, monitoring, drift detection, and incident-response plan. PM-side counterpart to engineering's mlops-reviewer. Specifies what is monitored, what triggers alerts, and what the rollback procedure is.