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-autogit 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-auto)<a href="https://agentmods.dev/skills/all-the-vibes/atv-phoenix/phoenix-auto"><img src="https://agentmods.dev/badge/skills/all-the-vibes/atv-phoenix/phoenix-auto/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-auto"><img src="https://agentmods.dev/badge/skills/all-the-vibes/atv-phoenix/phoenix-auto.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.00125 | $0.01091 |
| Opus 5 | $0.00063 | $0.00545 |
| Sonnet 5 | $0.00025 | $0.00218 |
| Haiku 4.5 | $0.00013 | $0.00109 |
Grade A, and why
phoenix-auto 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 12d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
phoenix-auto — the adaptive orchestrator
The base phoenix skill is a fixed routing tree (think → plan → build → review → ship): great
when the path is known. phoenix-auto is the dynamic counterpart — Anthropic's routing +
orchestrator-workers patterns (Building Effective Agents):
at each step it senses current state and picks the next skill based on results, because in real
work you can't predict the subtasks up front.
Fixed pipeline = a train on rails. phoenix-auto = a driver reading the road. Both are valid; pick by how predictable the path is.
The state-sensing loop
┌───────────────────────────────────────────────┐
▼ │
SENSE state ──▶ ROUTE to a skill ──▶ EXECUTE ──▶ phoenix_sense gate
(green/red? (pick next by (run it) │
backlog? current reality) ├─ green ─▶ snapshot, re-SENSE ─┘
stage?) └─ red ──▶ phoenix_heal (≤3) ─▶ re-SENSE
Routing policy (what to pick, given state)
| Current state | Route to |
|---|---|
| Goal is vague / no acceptance check exists | phoenix-goal (formalize) → or phoenix-think |
| Have intent, no steps | phoenix-plan |
| There's a backlog to grind to completion | phoenix-ralph (the persistence loop) |
| Implementing a known step | phoenix-build (+ phoenix-test to set the gate) |
| A check is red / something broke | phoenix-debug |
| Need cheap structural context | phoenix-context (graph) |
| Work looks complete | phoenix-review → phoenix-ship |
Guardrails (dynamic routing fails in specific, known ways — design against them)
- Oscillation guard. Keep a short route history. If you route to the same pair of skills back and forth, or pick the same skill 3× with no state change, stop and escalate — that's a planning problem, not a routing one.
- Confidence fallback. If the right next skill isn't clear, route to
phoenix-think, don't guess. - Re-sense, don't cache. Decide from a fresh read of state (the trace, the backlog, a real
phoenix_sense), never a remembered summary — stale state causes wrong routes. - Every executed step still ends in an objective gate. Routing chooses what;
phoenix_sensedecides whether it worked. Dynamic routing never relaxes the verification law. - Bounded. A cap on total steps; on exhaustion, report state honestly rather than looping.
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.
- 12d ago First seen · 71 lines · 125 tokens per session scan A 27a74b541f85
phoenix-auto is a skill published in the GitHub repository All-The-Vibes/ATV-Phoenix (5 stars, last pushed 8d ago), licensed MIT. It adds 125 tokens to every session and 1,091 once invoked, about $0.0006 per session on Opus 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
security-review
Perform a focused security review of pending git changes to identify high-confidence security vulnerabilities with real exploitation potential. Use this skill when the user asks for a security review, security audit, vulnerability scan, or wants to check pending changes on a branch for security issues before merging.…
huggingface-llm-trainer
Train or fine-tune language models with TRL or Unsloth on Hugging Face Jobs, including SFT, DPO, GRPO, reward models, and GGUF conversion. Use for cloud LLM training; use huggingface-vision-trainer for vision tasks.
feature-dev
Guide a feature implementation through a structured seven-phase workflow with deep codebase understanding, clarifying questions, parallel architecture design, and quality review. Use this skill when the user asks to build a new feature, add functionality, or wants a methodical approach to implementation rather than…
semgrep-rule-variant-creator
Creates language variants of existing Semgrep rules. Use when porting a Semgrep rule to specified target languages. Takes an existing rule and target languages as input, produces independent rule+test directories for each language.
learning-quality
Structured format for capturing high-quality learnings during ClosedLoop runs.
plan-validate
Deterministic plan.json validation via Python script, replacing most plan-validator agent calls. Performs JSON parsing, schema validation, task checkbox regex, required section checks, sync validation, and data extraction. Only semantic consistency checks (storage/query alignment) require the LLM agent. Triggers on…