eve-deploy-debugging

eve-deploy-debugging is a skill for Claude Code, Codex from Incept5/eve-skillpacks. It costs 23 tokens per session (2,847 once invoked), scanned A, original, MIT.

A workflow for deploying and diagnosing Eve-compatible applications in a staging environment, which is a separate setup used for testing before release.

In plain words
What is it for?
Use it to create or select a staging environment, deploy a specific code revision, pass deployment inputs, and poll the deployment for results.
Why use it?
It provides a defined way to deploy through the Eve command-line tool and investigate problems without directly changing shared Kubernetes infrastructure.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to create or select a staging environment, deploy a specific code revision, pass deployment inputs, and poll the deployment for results.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/incept5/eve-skillpacks/eve-deploy-debugging
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.

Any agent
npx skills add Incept5/eve-skillpacks --skill eve-deploy-debugging
Clone the repo
git clone --depth 1 https://github.com/Incept5/eve-skillpacks

Made for: Claude Code, Codex.

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 eve-deploy-debugging

README.md
[![agentmods](https://agentmods.dev/badge/skills/incept5/eve-skillpacks/eve-deploy-debugging/github.svg)](https://agentmods.dev/skills/incept5/eve-skillpacks/eve-deploy-debugging)
Your own site
<a href="https://agentmods.dev/skills/incept5/eve-skillpacks/eve-deploy-debugging"><img src="https://agentmods.dev/badge/skills/incept5/eve-skillpacks/eve-deploy-debugging/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.

agentmods 80×15 button for eve-deploy-debugging

Your own site · 80×15
<a href="https://agentmods.dev/skills/incept5/eve-skillpacks/eve-deploy-debugging"><img src="https://agentmods.dev/badge/skills/incept5/eve-skillpacks/eve-deploy-debugging.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,847 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00023 $0.02847
Opus 5.5 $0.00009 $0.01139
Sonnet 5.5 $0.00005 $0.00569
Haiku 4.5 $0.00002 $0.00285

Measured 2mo ago against content hash 17fbed00d462, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

eve-deploy-debugging 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 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.

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.

eve-se/eve-deploy-debugging/SKILL.md · 315 lines

How it starts

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

Eve Deploy and Debug

Use these steps to deploy and diagnose app issues quickly.

Environment Setup

  • Get the staging API URL from your admin.
  • Create and use a profile:
eve profile create staging --api-url https://api.eve.example.com
eve profile use staging

Infrastructure Change Policy

Never run kubectl apply, helm install, or any direct Kubernetes resource creation against shared infrastructure. All infrastructure changes go through Terraform. Use the Eve CLI (eve env, eve env deploy) to manage application deployments — the platform handles the underlying k8s resources.

Deploy Flow (Staging)

# Create env if needed
eve env create staging --project proj_xxx --type persistent

# Deploy (requires --ref with 40-char SHA or a ref resolved against --repo-dir)
eve env deploy staging --ref main --repo-dir .

# When environment has a pipeline configured, the above triggers the pipeline.
# Use --direct to bypass pipeline and deploy directly:
eve env deploy staging --ref main --repo-dir . --direct

# Pass inputs to pipeline:
eve env deploy staging --ref main --repo-dir . --inputs '{"key":"value"}'

Deploy Polling Flow

When eve env deploy is called:

  1. Direct deploy (no pipeline): Returns deployment_status directly. Poll health endpoint until ready === true.
  2. Pipeline deploy: Returns pipeline_run_id. Poll GET /pipelines/{name}/runs/{id} until all steps complete, then check health.

Deploy is complete when: ready === true AND active_pipeline_run === null.

Observe the Deploy

eve job list --phase active
eve job follow <job-id>              # Real-time SSE streaming
eve job watch <job-id>               # Poll-based status updates
eve job diagnose <job-id>            # Full diagnostic
eve job result <job-id>              # Final result
eve job runner-logs <job-id>         # Raw worker logs

Real-Time Debugging (3-Terminal Approach)

# Terminal 1: Pipeline/job progress
eve job follow <job-id>

# Terminal 2: Environment health
eve env diagnose <project> <env>

# Terminal 3: System-level logs
eve system logs

Read the full file on GitHub · 315 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. 2mo ago First seen · 315 lines · 23 tokens per session scan A 17fbed00d462

Subscribe to this mod's changes

eve-deploy-debugging is a skill published in the GitHub repository Incept5/eve-skillpacks (0 stars, last pushed 4mo ago), licensed MIT. It adds 23 tokens to every session and 2,847 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

cwv-optimizer

Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…

adobe/skills · 112 tokens

ci-fixer

CI failures - read error, minimal fix, verify.

sipyourdrink-ltd/bernstein · 15 tokens

incident-response-incident-response

Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.

rmyndharis/antigravity-skills · 36 tokens

diagnosing-missing-recordings

Diagnoses why a session recording is missing or was not captured. Use when a user asks why a session has no replay, why recordings aren't appearing, or wants to troubleshoot session replay capture issues for a specific session ID or across their project. Covers SDK diagnostic signals, project settings, sampling…

PostHog/posthog · 76 tokens