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 All-The-Vibes/ATV-Phoenix --skill phoenix-debuggit clone --depth 1 https://github.com/All-The-Vibes/ATV-PhoenixWrote 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/all-the-vibes/atv-phoenix/phoenix-debug)<a href="https://agentmods.dev/skills/all-the-vibes/atv-phoenix/phoenix-debug"><img src="https://agentmods.dev/badge/skills/all-the-vibes/atv-phoenix/phoenix-debug/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/all-the-vibes/atv-phoenix/phoenix-debug"><img src="https://agentmods.dev/badge/skills/all-the-vibes/atv-phoenix/phoenix-debug.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.00080 | $0.01158 |
| Opus 5.5 | $0.00032 | $0.00463 |
| Sonnet 5.5 | $0.00016 | $0.00232 |
| Haiku 4.5 | $0.00008 | $0.00116 |
Grade A, and why
phoenix-debug 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 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.
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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
phoenix-debug — reproduce, isolate, fix the root, prove it healed
Overview
When something breaks, the failure mode is guessing. Phoenix debugging is evidence-driven: first capture
the failure as a runnable phoenix_sense check (so you can prove when it's fixed), then isolate the
cause using the code graph instead of reading the whole repo, fix the root not the symptom, and
confirm green. Recovery is real only when the check that was red is green — and you watched it happen.
When to use
- A
phoenix_sensecheck went red and you don't immediately know why. - A regression: something that passed now fails.
- An error/stack trace you need to chase down.
When NOT to use: you already know the exact one-line fix and have a check — just phoenix-build it.
The triage flow
Break observed
│
▼
1. REPRODUCE → capture as a phoenix_sense check that is RED now
│
▼
2. ISOLATE → graph: who calls / what changed near the failure (NOT grep the repo)
│
▼
3. HYPOTHESIZE→ smallest plausible root cause
│
▼
4. FIX root → snapshot, edit, phoenix_sense
│ ├── green ─► verify no regressions (full suite) ─► done
│ └── red ──► phoenix_heal rollback ─► new hypothesis (≤3 cycles)
▼
5. If 3 cycles fail → STOP, report findings + what you ruled out
1. Reproduce as a check (don't fix blind)
Turn the break into the narrowest red phoenix_sense you can. If it's an intermittent failure, try
phoenix_heal retry first to learn whether it's transient or real. You cannot prove a fix without a
reproducer.
2. Isolate with the graph, not grep
Ask phoenix-context: "who calls the failing function?", "what changed in its blast radius?",
"what does it depend on?". This finds the cause in a bounded query instead of re-reading files turn
after turn (which burns the context budget exactly when you need it most).
3. Fix the root, not the symptom
Patching the symptom (swallowing the exception, special-casing the one failing input) leaves the real bug live. Trace to the actual cause. If you can only treat the symptom, say so explicitly and open a follow-up — don't pretend the root is fixed.
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 · 89 lines · 80 tokens per session scan A 09ad8937b7fa
phoenix-debug is a skill published in the GitHub repository All-The-Vibes/ATV-Phoenix (6 stars, last pushed 6d ago), licensed MIT. It adds 80 tokens to every session and 1,158 once invoked, about $0.0003 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
pipeline-validator
Discovers, triggers, and monitors Azure DevOps pipelines (PR, Buddy Build, Buddy Release) for the current repo and branch. Auto-diagnoses failures from build logs, applies fixes, commits, pushes, and re-triggers until all pipelines pass or max retries reached. Validates PR existence and description completeness.…
ai-agents-empirical-probe-toolkit
Prove-it methods for this repo. Six recipes for runtime-contract probes, guard and threshold calibration, eval A/B, docs-vs-reality audits, reproduce-on-main CI triage, and negative-control test design, each with a worked example from repo history. Use when you say probe the runtime contract, calibrate this guard…
taste-lints
Use when you say run taste lints, check file size, or lint taste invariants. Custom lints with agent-readable remediation instructions for file size, naming conventions, structured logging, and complexity.
ai-agents-config-catalog
Catalog of every configuration axis in this repo, env vars, commit markers, frontmatter keys, QA skip verdicts, and escape hatches, each with its enforcement point and abuse story, plus the checklist for adding a new flag safely. Use when you say what does a skip flag do, list escape hatches, can I skip this gate, add…
ai-agents-debugging-playbook
Symptom-to-triage playbook for this repo's recurring failures. Blocked pushes, drift gate reds, plugin bump reds, coverage pin trips, hook exit 143, session NONCOMPLIANT. Maps each symptom to a first command, discriminating experiment, fix path, and trap. Use when you say triage this failure, why is my push blocked…
apex-debug-log-export
Bundle selected native Copilot SDK events locally for manual inspection or upload. Use /apex-debug-log-export inside VS Code after selecting the built-in agent owner and MAI-Code-1.1-Flash. Explicit workspace/session scope; no automatic upload.