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-testgit 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-test)<a href="https://agentmods.dev/skills/all-the-vibes/atv-phoenix/phoenix-test"><img src="https://agentmods.dev/badge/skills/all-the-vibes/atv-phoenix/phoenix-test/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-test"><img src="https://agentmods.dev/badge/skills/all-the-vibes/atv-phoenix/phoenix-test.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.00087 | $0.01134 |
| Opus 5 | $0.00044 | $0.00567 |
| Sonnet 5 | $0.00017 | $0.00227 |
| Haiku 4.5 | $0.00009 | $0.00113 |
Grade A, and why
phoenix-test 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 10d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
phoenix-test — the test is the gate; red→green is proven, not asserted
Overview
Write a failing test before the code that makes it pass. For a bug, reproduce it with a test before
attempting a fix. In Phoenix, the test is not a suggestion — it is the literal phoenix_sense check
that gates the work. "Seems right" is never done; a red→green transition you watched happen is. A
codebase with tests is the agent's superpower because it converts judgment into objective signal.
When to use
- Implementing any new logic or behavior.
- Fixing any bug (the Prove-It Pattern below).
- Modifying existing functionality or adding edge-case handling.
When NOT to use: pure config/doc/static changes with no behavioral impact (a lint sense is enough).
The cycle — RED → GREEN → REFACTOR, each step a phoenix_sense
RED GREEN REFACTOR
write a test write minimal code clean up, no
that FAILS ──► to make it pass ──► behavior change ──► (repeat)
│ │ │
phoenix_sense phoenix_sense phoenix_sense
= ok:false = ok:true = still ok:true
1. RED — write the failing test, and sense it fail
A test that passes immediately proves nothing. Run it and confirm red:
phoenix_sense {"kind":"command_exit","target":["pytest","-q","tests/test_task.py::test_create"],"expect":0}
# -> {"ok":false} ← REQUIRED. If this is green, the test isn't testing the new behavior.
2. GREEN — minimal code, then sense it pass
Write the least code that turns the check green. Don't over-engineer. Re-sense the same check → ok:true.
3. REFACTOR — improve with the check as a guardrail
phoenix_snapshot the file, refactor, phoenix_sense after each change. If a refactor goes red,
phoenix_heal rollback — the refactor is supposed to be behavior-preserving, so red means you changed
behavior. Roll back and try a smaller refactor.
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.
- 10d ago First seen · 81 lines · 87 tokens per session scan A d99d5bf1d7c0
phoenix-test is a skill published in the GitHub repository All-The-Vibes/ATV-Phoenix (5 stars, last pushed 6d ago), licensed MIT. It adds 87 tokens to every session and 1,134 once invoked, about $0.0004 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
hotfix
Fixes an observed defect with reproducible evidence in one call: writes a short trace doc before touching code, implements the fix, and backs it with a regression test written before the fix. Production incidents are the motivating case, not a gate. When blocked, it halts by name and saves the doc for a later call to…
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.
testing-checklist
Testing checklist — test pyramid, what to test vs skip, DAMP over DRY, the TDD red-green-refactor loop for new code, failing-test-first for bug fixes, Vitest / React Testing Library patterns. Use when writing or reviewing tests, deciding test coverage for a change, driving new code test-first, fixing a bug (regression…
Test Driven Development
Strict Red-Green-Refactor implementation methodology for high quality, regression-free software.
unit-testing
Implement or extend production behavior test-first, or diagnose focused unit-test quality and flakiness, using red-green-refactor, ZOMBIES, Tidy First?, FIRST microtests, and Save Your Game checkpoints. Use for TDD, microtests, test-first bug fixes, flaky tests, and refactoring within an active green cycle. Do not use…
test-strategy
Produces a test strategy document defining what to test, at which layer, with which tools, and to what coverage standard. It applies the test pyramid model, surfaces coverage gaps in existing codebases, and produces a concrete plan — not a generic "write more tests" recommendation.