Borrowing it
Nothing to install: this file belongs to different-ai/agent-bank. 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/different-ai/agent-bank/main/.opencode/skill/debug-prod-issues/SKILL.mdgit clone --depth 1 https://github.com/different-ai/agent-bankWrote 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/different-ai/agent-bank/debug-prod-issues)<a href="https://agentmods.dev/skills/different-ai/agent-bank/debug-prod-issues"><img src="https://agentmods.dev/badge/skills/different-ai/agent-bank/debug-prod-issues/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/different-ai/agent-bank/debug-prod-issues"><img src="https://agentmods.dev/badge/skills/different-ai/agent-bank/debug-prod-issues.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.00021 | $0.02124 |
| Opus 5.5 | $0.00008 | $0.00850 |
| Sonnet 5.5 | $0.00004 | $0.00425 |
| Haiku 4.5 | $0.00002 | $0.00212 |
Grade A, and why
debug prod issues 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.
3. Test with curl to see response: How it starts
The opening of the file, as written. The whole thing — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What I Do
- Debug production issues on Vercel
- View and filter Vercel function logs
- Wait for deployments correctly
- Connect to production Neon database
- Inspect tables and data for debugging
Vercel Debugging (0 Finance)
IMPORTANT: Always use --scope prologe for the 0 Finance project:
# All Vercel commands need --scope prologe
vercel logs www.0.finance --scope prologe
vercel ls --scope prologe
vercel env ls --scope prologe
Viewing Logs
# Stream live logs (waits for new logs)
vercel logs www.0.finance --scope prologe
# Logs since a specific time
vercel logs www.0.finance --scope prologe --since 5m
vercel logs www.0.finance --scope prologe --since 1h
# Filter logs (pipe to grep)
vercel logs www.0.finance --scope prologe 2>&1 | grep -i "error"
vercel logs www.0.finance --scope prologe 2>&1 | grep "ai-email"
Note: vercel logs can be slow/hang. Use timeout or Ctrl+C if needed:
timeout 30 vercel logs www.0.finance --scope prologe --since 5m 2>&1 | head -100
Checking Deployments
# List recent deployments
vercel ls --scope prologe | head -10
# Check specific deployment status
vercel inspect <deployment-url> --scope prologe
# Get latest deployment URL
vercel ls --scope prologe 2>/dev/null | head -1
Waiting for Deployments
DO NOT just sleep and hope. Use vercel inspect --wait:
# Get the latest deployment URL
LATEST=$(vercel ls --scope prologe 2>/dev/null | head -1)
# Wait for it to be ready (up to 5 minutes)
vercel inspect "$LATEST" --scope prologe --wait --timeout 5m
# Check the status in the output:
# status: ● Building -> still building
# status: ● Ready -> deployed and live!
# status: ● Error -> build failed
Full workflow after pushing code:
# 1. Push your changes
git push origin main
# 2. Wait a few seconds for Vercel to pick it up
sleep 5
# 3. Get the new deployment URL
LATEST=$(vercel ls --scope prologe 2>/dev/null | head -1)
echo "Waiting for: $LATEST"
# 4. Wait for it to complete
vercel inspect "$LATEST" --scope prologe --wait --timeout 5m
# 5. Now your changes are live!
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 · 325 lines · 21 tokens per session scan A 4afe3b8a8742
debug prod issues is a skill published in the GitHub repository different-ai/agent-bank (255 stars, last pushed 6mo ago), licensed MIT. It adds 21 tokens to every session and 2,124 once invoked, about $0.0001 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
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…
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.
ci-fixer
CI failures - read error, minimal fix, verify.