Borrowing it
Nothing to install: this file belongs to zpoint/vibe-seller. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/zpoint/vibe-seller/main/.claude/skills/debug-task/SKILL.mdgit clone --depth 1 https://github.com/zpoint/vibe-sellerWrote 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/zpoint/vibe-seller/debug-task)<a href="https://agentmods.dev/skills/zpoint/vibe-seller/debug-task"><img src="https://agentmods.dev/badge/skills/zpoint/vibe-seller/debug-task/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/zpoint/vibe-seller/debug-task"><img src="https://agentmods.dev/badge/skills/zpoint/vibe-seller/debug-task.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 414 Code scans file system directories looking for sensitive files. This could be reconnaissance for credential theft.Fix: Remove unnecessary filesystem scanning. If file access is needed, use explicit, scoped paths. Avoid reading ~/.ssh, ~/.aws, or credential directories.
- medium Data Exfiltration · line 415 Code scans file system directories looking for sensitive files. This could be reconnaissance for credential theft.Fix: Remove unnecessary filesystem scanning. If file access is needed, use explicit, scoped paths. Avoid reading ~/.ssh, ~/.aws, or credential directories.
- medium Agent Snooping · line 415 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00031 | $0.05816 |
| Opus 5.5 | $0.00012 | $0.02326 |
| Sonnet 5.5 | $0.00006 | $0.01163 |
| Haiku 4.5 | $0.00003 | $0.00582 |
Grade B, and why
debug-task scanned grade B 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 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
ls -la ~/.vibe-seller/tasks/{task_id}/.claude/skills/ Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -m3 http://127.0.0.1:7777/api/auth/me # 200 with a user → a server is up How it starts
The opening of the file, as written. The whole thing — 493 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Task Infra
Debug agent task execution infrastructure issues by analyzing agent logs.
Core Philosophy
Every agent failure, detour, or workaround is an infra/platform bug — not an agent problem.
When an agent:
- Tries a wrong file path then searches for the right one → catalog or path resolution bug
- Uses wrong CLI syntax then self-corrects → skill docs not loaded or incomplete
- Takes a screenshot but can't find/view it → tool integration bug
- Retries a command with different args → missing docs or unclear API
- Reflects "no failures" when there were failures → reflection prompt bug
Even if the agent eventually succeeds, each detour:
- Wastes tokens and time
- Signals a gap in the platform that WILL hit other tasks
- Must be traced to a specific infra root cause and filed as a bug
Do NOT dismiss detours as "the agent will self-correct." Your job is to find every single failure step, trace it to a code/config/prompt root cause, and report it.
When to use
When a task execution shows symptoms like:
- Agent sees unexpected files or can't find expected ones
- Agent runs in wrong working directory
- Browser (Ziniao/Chrome) fails to start or takes multiple retries
- Task uses wrong Python environment
- Store context (bookmarks, browser config) missing from agent prompt
- Agent repeats same bash command 3+ times (infra issue, not agent fault)
- Agent repeats browser-open attempts (browser startup failure)
- Agent can't load skills (wrong skill path or skill not synced)
- Agent passes wrong arguments to tools (schema mismatch)
- Agent uses workarounds for things that should "just work"
- Agent's post-task reflection misses failures that clearly happened
Environment first: are you in WSL debugging a native-Windows server?
Before running ANY command below, figure out where the server actually runs. vibe-seller ships as a native-Windows install and as a Linux/WSL install, and the two do not share a data directory. Debugging the wrong one is the single biggest time-sink — you'll read a stale DB, grep empty logs, and "fix" a store that isn't the one serving traffic.
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 · 493 lines · 31 tokens per session scan B 84e4db3ec136
debug-task is a skill published in the GitHub repository zpoint/vibe-seller (102 stars, last pushed today), licensed Apache-2.0. It adds 31 tokens to every session and 5,816 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 2 findings (enumerates other installed skills, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
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…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
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…
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.