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 Incept5/eve-skillpacks --skill eve-job-debugginggit clone --depth 1 https://github.com/Incept5/eve-skillpacksWrote 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/incept5/eve-skillpacks/eve-job-debugging)<a href="https://agentmods.dev/skills/incept5/eve-skillpacks/eve-job-debugging"><img src="https://agentmods.dev/badge/skills/incept5/eve-skillpacks/eve-job-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.
<a href="https://agentmods.dev/skills/incept5/eve-skillpacks/eve-job-debugging"><img src="https://agentmods.dev/badge/skills/incept5/eve-skillpacks/eve-job-debugging.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.00036 | $0.00787 |
| Opus 5.5 | $0.00014 | $0.00315 |
| Sonnet 5.5 | $0.00007 | $0.00157 |
| Haiku 4.5 | $0.00004 | $0.00079 |
Grade A, and why
eve-job-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.
How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eve Job Debugging
CLI-Only Debugging
Debug via the Eve CLI exclusively. This replicates the client experience — clients don't have kubectl or host access.
Every debugging capability must be available through the CLI. If you find yourself needing system tools to diagnose a job issue, that's a gap in our CLI that should be fixed.
Monitor
eve job follow <id>to stream logs.eve job wait <id> --timeout 300 --jsonto wait on completion.eve job result <id> --format textfor the latest result.
Diagnose
eve job diagnose <id>for timeline and error summary.eve job show <id> --verbosefor attempts and phase.eve job dep list <id>for dependency blocks.
Per-Job Harness Overrides
When debugging unexpected harness behavior, suspect a per-job override before suspecting agent defaults. Jobs may carry inline overrides set at create time:
--harness-override-file <path.json>— inline{harness, model?, reasoning_effort?, variant?, temperature?}bundle that wins overharness_profile.--env-override KEY=VALUE(repeatable) — per-job env values, may include${secret.KEY}placeholders resolved at spawn.
Both fields persist on the job record (harness_profile_override, env_overrides) and on each attempt (harness_profile_source, harness_profile_hash). Inspect via eve job show <id> --json and check the routing log entry on the attempt for the resolved harness_profile_source (agent_default, string_ref, inline_override, or workflow_template). Missing-secret interpolation fails fast with error_code: missing_secret_override.
Stuck Jobs
The orchestrator now self-heals from agent-runtime pod loss — these no longer leave jobs stuck:
- Pod death mid-execution:
recoverActiveJobsWithTerminatedAttemptssweep reclaims active jobs whose attempts were externally finalized, releases limiter slots, and closes workflow roots. - Graceful shutdown: agent-runtime preStop marks running attempts as
pod_terminatedand sets pod status todrainingso no new routing lands on it. - Stale recovery: covers all assignee types (not just
orchestrator), so agent-assigned jobs (e.g.map-generator,pm-coordinator) are visible to the watchdog.
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 · 55 lines · 36 tokens per session scan A 3facf2020d36
eve-job-debugging is a skill published in the GitHub repository Incept5/eve-skillpacks (0 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 787 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.
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.
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…
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…
ci-fixer
CI failures - read error, minimal fix, verify.
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.
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…