deploio-debug

deploio-debug is a skill for Claude Code from renuo/deploio-claude-plugin. It costs 179 tokens per session (3,319 once invoked), scanned C, original, MIT.

A troubleshooting skill for Deploio applications, a platform for running deployed apps. It investigates crashes, failed builds or releases, startup problems, and server errors such as 500 or 503 responses.

In plain words
What is it for?
Use it when a Deploio app is crashing, failing to build or deploy, refusing to start, or returning server errors.
Why use it?
It helps narrow a deployment or runtime problem to its underlying cause instead of only displaying raw logs. It gathers information from the app's status, logs, and release history.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: names the AskUserQuestion tool.

Part of the deploio plugin — 5 skills, 2 commands, 1 agent shipped together

Good fit Use it when a Deploio app is crashing, failing to build or deploy, refusing to start, or returning server errors.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/renuo/deploio-claude-plugin/deploio-debug
Install

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.

agentmods
npx agentmods add skills/renuo/deploio-claude-plugin/deploio-debug
Any agent
npx skills add renuo/deploio-claude-plugin --skill deploio-debug
Clone the repo
git clone --depth 1 https://github.com/renuo/deploio-claude-plugin

Made for: Claude Code.

Or install deploio, the plugin that ships this one along with the rest of its 5 skills, 2 commands, 1 agent.

Wrote 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.

agentmods badge for deploio-debug

README.md
[![agentmods](https://agentmods.dev/badge/skills/renuo/deploio-claude-plugin/deploio-debug.svg)](https://agentmods.dev/skills/renuo/deploio-claude-plugin/deploio-debug)
Your own site
<a href="https://agentmods.dev/skills/renuo/deploio-claude-plugin/deploio-debug"><img src="https://agentmods.dev/badge/skills/renuo/deploio-claude-plugin/deploio-debug.svg" alt="Measured on agentmods" height="20"></a>
Per session 179 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,319 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00179 $0.03319
Opus 5 $0.00089 $0.01659
Sonnet 5 $0.00036 $0.00664
Haiku 4.5 $0.00018 $0.00332

Measured 6d ago against content hash 86d1fa538f21, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade C, and why

deploio-debug scanned grade C with 2 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 6d 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.

Harvests environment variableshighData exfiltration

Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.

nctl exec app <name> --project <project> -- env | grep SECRET

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

nctl exec app <name> --project <project> -- curl -s http://localhost:3000/up
skills/deploio-debug/SKILL.md · 295 lines

How it starts

The opening of the file, as written. The whole thing — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Deploio: Debugging and Troubleshooting

Your role is coordinator. You never run commands yourself — you spawn deploio-cli agents with mode: bypassPermissions to gather diagnostics and run exec sessions. The goal is to identify the root cause and propose a fix, not just dump logs.

Communication style: Speak to the user in plain language — describe what you found and what you'll do, never paste raw nctl commands. Say "I'm pulling the recent logs and release history" not "I'll run nctl logs app ... -l 200". Agents manage the CLI entirely on the user's behalf.

Parallel agents: When investigating multiple stages at once (e.g. downtime with no clear cause), spawn two or more agents simultaneously — one for build/deploy logs, another for app status and release history. Don't wait for the first to finish before starting the second.


Phase 0: Classify the failure stage

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 and proceed immediately: "Investigating app main in project renuotest-myapp (org renuotest) — let me know if that's different." Only ask if there is no git remote, or if nctl fails because the organization doesn't exist.

If the app can be inferred, investigate autonomously — do not wait for the user to describe the symptom. Spawn diagnostic agents to gather logs, status, and release history, then report your findings. The user can always provide more context, but proactive investigation is faster and more useful.

From the conversation, classify the symptom to target the right logs:

Symptom Failure stage Phase 1 target
Build error, "bundle install failed", "npm error", "Dockerfile error" Build build logs
"migrations failed", "deploy job timed out" Deploy job deploy_job logs
"release stuck", "release failed" Release releases + app logs
App crashes immediately after deploy Boot app logs
App running but returning errors (500, 502, 503) Runtime app logs + exec
Worker not processing, job queue backed up Worker worker_job logs

Read the full file on GitHub · 295 lines

Changes

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.

  1. 6d ago First seen · 295 lines · 0 tokens per session scan C 86d1fa538f21

Subscribe to this mod's changes

deploio-debug is a skill published in the GitHub repository renuo/deploio-claude-plugin (3 stars, last pushed 2mo ago), licensed MIT. It adds 179 tokens to every session and 3,319 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it C with 2 findings (harvests environment variables, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

debugging-workflows

Systematic troubleshooting for Falcon Foundry CLI errors, manifest validation failures, deploy failures, artifact runtime errors, and development server issues. TRIGGER when user encounters CLI errors, foundry ui run not working, deploy failures, authentication issues, function execution failures, "debug my function"…

CrowdStrike/foundry-skills · 90 tokens

release-it

Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "deployment pipeline", "chaos engineering", "retry storm", "health checks", "my service keeps crashing", "prevent cascading failures", or…

wondelai/skills · 131 tokens

tidewave-integration

Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.

oliver-kriska/claude-elixir-phoenix · 38 tokens

debug

Interactive debugging workflow with hypothesis-driven probe loop. Use when: unknown bugs, script errors, silent failures, troubleshooting. Not for: known bugs (use bug-fix), GitHub issue analysis (use issue-analyze), code understanding (use code-explore). Output: debug report with probe journal + root cause + fix.

sd0xdev/sd0x-harness · 67 tokens

git-investigate

Git history investigation. Use when: tracking code changes, finding where bugs were introduced, root cause analysis. Not for: code exploration (use code-explore), issue analysis (use issue-analyze). Output: history trace + root cause report.

sd0xdev/sd0x-harness · 53 tokens

analyze

Deep-dive codebase analysis that explains how things actually work — business rules, architecture patterns, auth flows, data models, integrations, and performance hotspots. Use whenever the user asks "how does X work", "map the Y flow", "what are the business rules for Z", "trace the auth path", "explore the codebase…

rsmdt/the-startup · 118 tokens