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-store/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-store)<a href="https://agentmods.dev/skills/zpoint/vibe-seller/debug-store"><img src="https://agentmods.dev/badge/skills/zpoint/vibe-seller/debug-store/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-store"><img src="https://agentmods.dev/badge/skills/zpoint/vibe-seller/debug-store.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 7 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 Rogue Agent · line 66 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Data Exfiltration · line 181 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Rogue Agent · line 315 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Data Exfiltration · line 330 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 377 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Rogue Agent · line 406 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Data Exfiltration · line 424 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00121 | $0.07304 |
| Opus 5.5 | $0.00048 | $0.02922 |
| Sonnet 5.5 | $0.00024 | $0.01461 |
| Haiku 4.5 | $0.00012 | $0.00730 |
Grade A, and why
debug-store scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sf -m 2 --noproxy '*' "http://127.0.0.1:$PORT/json/version" How it starts
The opening of the file, as written. The whole thing — 598 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Store Infrastructure (developer-only)
This is the inside-out view of vibe-seller stores: how to inspect and drive the runtime — the database, the browser-use wrapper, the CDP proxy, the per-store Ziniao session — without going through the task system, the web UI, or the JWT-cookie auth wall.
This is for the platform builder, not for end-user agents running tasks.
For end-user/agent flows (running campaigns, etc.), see amazon-ads and
new-product-launch.
What you can do without a task
The vibe-seller per-store wrapper is just a shell script that talks to
a long-running CDP-mux proxy. The wrapper auto-starts the proxy and
the browser via an internal API call (with a baked-in ai_bot JWT,
so you don't need user creds). All you need is:
- A fresh
VIBE_TASK_IDenv var (lowercase UUID; first 8 chars must be hex). - The store slug (look it up in
~/.vibe-seller/data/vibe_seller.db—stores.name, then slugify; or just list~/.vibe-seller/bin/for the directories that actually exist).
Then ~/.vibe-seller/bin/<slug>/browser-use open <url> works.
DB cheatsheet
DB=~/.vibe-seller/data/vibe_seller.db
sqlite3 "$DB" .tables
sqlite3 "$DB" "SELECT id, name, browser_backend, platforms, countries FROM stores;"
sqlite3 "$DB" ".schema stores"
sqlite3 "$DB" "SELECT id, username, email, role FROM users;"
sqlite3 "$DB" "SELECT store_id, status, current_platform, current_country,
active_tab_count, cdp_port, chrome_pid
FROM browser_sessions;"
sqlite3 "$DB" "SELECT id, status, substr(result,1,120), substr(error,1,120)
FROM tasks WHERE created_at > datetime('now','-1 hour')
ORDER BY created_at DESC LIMIT 10;"
The stores table has no slug column — the wrapper directory
(~/.vibe-seller/bin/<slug>/) is where the actual usable name lives.
name in DB is the user-facing label and may differ from the slug
when names contain spaces / non-ascii. Match by ID when scripting.
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 · 598 lines · 121 tokens per session scan A 3f2d8b2c6c04
debug-store is a skill published in the GitHub repository zpoint/vibe-seller (102 stars, last pushed today), licensed Apache-2.0. It adds 121 tokens to every session and 7,304 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 1 finding (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
revenuecat-troubleshoot
Diagnose and resolve RevenueCat integration issues — inspects dashboard configuration through the RevenueCat MCP, walks the SDK debug logs, and covers code-side gotchas. Use when the user says offerings are empty, products not loading, entitlement not active after purchase, paywall won't load, transactions not…
b2c-logs
Retrieve and search logs from B2C Commerce instances using the b2c CLI. Use this skill whenever the user needs to view server logs, search for errors, filter log entries by level or time, or monitor logs in real-time. Also use when the user reports a 500 error, broken checkout, failing job, or any server-side issue…
vendure-troubleshooting
Diagnose a broken or misbehaving Vendure project. Use when a Vendure server or worker does not start, migrations fail or are pending, @vendure/ or plugin versions do not match, assets or emails do not work, or an upgrade to the next 3.x minor breaks something. Collects local project context first, then follows the…
wcs-health-check-processing
WooCommerce Subscriptions 8.8+ Health Check and Processing Reliability playbook for missing renewal schedules, automatic-renewal candidates, guarded Resolve actions, dedicated Action Scheduler processing, web cron, health-check tables, logs, AJAX nonces, and queue filters. Use for WCS Health Check…
wc-logging
Add production-safe WooCommerce logs with wcgetlogger(). Covers stable sources, severity levels and thresholds, structured JSON context, correlation IDs, sensitive-data redaction, WooCommerce 11.0 file-v2 formatting and batched retention cleanup, volume control, custom handlers, and why logs are not durable business…
sfcc-webdav-workflows
Practical guide for using WebDAV in Salesforce B2C Commerce Cloud for IMPEX transfers and log access. Use this when setting up WebDAV clients, debugging WebDAV permission issues, or designing automation that reads/writes files via WebDAV.