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/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/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/agents/renuo/deploio-claude-plugin/deploio-cli"><img src="https://agentmods.dev/badge/agents/renuo/deploio-claude-plugin/deploio-cli.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.00081 | $0.03042 |
| Opus 5.5 | $0.00032 | $0.01217 |
| Sonnet 5.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 1mo 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.
- 1mo 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 21d ago), licensed MIT. It adds 81 tokens to every session and 3,042 once invoked, about $0.0003 per session on Opus 5.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
github-actions-expert
Use this agent when you need expert GitHub Actions workflow development, CI/CD pipeline optimization, and security hardening. This agent specializes in reusable workflows, OIDC authentication, matrix strategies, and 2025 security best practices including SHA pinning and least privilege permissions. Examples: Context…
production
Production readiness audit specialist for repo-doctor. Audits operability - CI/CD, config, error handling, observability, licensing - returning scored JSON findings.
devops-agent
DevOps/Infrastructure agent — CI/CD pipelines, Kubernetes, Terraform IaC, Docker, monitoring, deployment strategies. Multi-cloud (AWS, GCP, Azure, Cloudflare). Use for: infrastructure work, pipelines, K8s, Docker, Terraform, Helm, GitOps, DevSecOps, FinOps. Triggers on: "DevOps", "infra", "pipeline", "CI/CD"…
devops-engineer
CI/CD and infrastructure automation expert.
powershell-7-expert
Use when building cross-platform cloud automation scripts, Azure infrastructure orchestration, or CI/CD pipelines requiring PowerShell 7+ with modern .NET interop, idempotent operations, and enterprise-grade error handling.
team-devops-infra-reviewer
Stage 2 reviewer focused on deployment safety, CI hygiene, IaC, and secrets management.