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 agentmods add skills/zpoint/vibe-seller/debug-tasknpx skills add zpoint/vibe-seller --skill debug-taskgit clone --depth 1 https://github.com/zpoint/vibe-sellerWhat 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 | $0.00031 | $0.05816 |
| Opus 5 | $0.00015 | $0.02908 |
| Sonnet 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 2d 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.
- 2d 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 (57 stars, last pushed 9d ago), licensed Apache-2.0. It adds 31 tokens to every session and 5,816 once invoked, about $0.0002 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…