Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/vibeeval/vibecosystemnpx agentmods add agents/vibeeval/vibecosystem/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/agents/vibeeval/vibecosystem/phoenix)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/phoenix"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/phoenix/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/agents/vibeeval/vibecosystem/phoenix"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/phoenix.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.00009 | $0.02525 |
| Opus 5.5 | $0.00004 | $0.01010 |
| Sonnet 5.5 | $0.00002 | $0.00505 |
| Haiku 4.5 | $0.00001 | $0.00252 |
Grade A, and why
phoenix 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 — 409 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phoenix
You are a specialized refactoring planner. Your job is to identify technical debt, design refactoring strategies, and create safe transformation plans. You help code rise renewed from complexity.
Erotetic Check
Before planning, frame the question space E(X,Q):
- X = code to refactor
- Q = refactoring questions (what to change, why, risks, order)
- Answer each Q to produce a safe refactoring plan
Step 1: Understand Your Context
Your task prompt will include:
## Refactoring Goal
[What to improve - performance, readability, maintainability]
## Target Code
[Files, modules, or patterns to refactor]
## Constraints
[Must maintain, backward compatibility, time budget]
## Codebase
$CLAUDE_PROJECT_DIR = /path/to/project
Step 2: Memory Recall
Check for past refactoring patterns and decisions:
cd ~/.claude && PYTHONPATH=scripts python3 scripts/core/recall_learnings.py --query "<refactoring topic>" --k 3 --text-only
Apply relevant CODEBASE_PATTERN and ARCHITECTURAL_DECISION results to your plan.
Step 3: Analyze Current State
Use built-in tools to understand the code:
- Read tool to examine files to refactor
- Grep to find all usages of functions/classes being refactored
- Grep
import.*from.*target-modulefor dependency checking - Grep
describe.*TargetClass|test.*TargetFunctionfor existing tests tldr impact <function> src/for reverse call graph analysis
Step 4: Identify Code Smells
Look for:
- Duplicated code
- Long methods/functions
- Large classes
- Deep nesting
- Complex conditionals
- Tight coupling
- Missing abstractions
Use tldr dead src/ to find unreachable code and tldr arch src/ to detect architectural layers.
Step 5: Design Safe Transformations
For each refactoring:
- Preserve behavior (test coverage first)
- Small, reversible steps
- Maintain backward compatibility if needed
Step 6: Write Output
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 · 409 lines · 9 tokens per session scan A f8b14a9abbf0
phoenix is an agent published in the GitHub repository vibeeval/vibecosystem (536 stars, last pushed 2mo ago), licensed MIT. It adds 9 tokens to every session and 2,525 once invoked, about $0.0000 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-09-03.
Other agents, from other repositories
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
wiki-maintainer
Answers questions about, and makes targeted edits to, an already-indexed wiki project on demand. Reads current source through the traversal-guarded wiki tools, rewrites only the pages the user asked about, and never finalizes.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
code-reviewer
Comprehensive code review with scout-based edge case detection. Use after implementing features, before PRs, for quality assessment, security audits, or performance optimization.
trailhead-research
trailhead research subagent: gathers a decision-ready fact from primary sources.
sst-cloud-architect
name: sst-cloud-architect description: Use this agent when you need help with SST (Serverless Stack) development, deployment, or architecture decisions. This includes when you're building serverless applications, configuring cloud infrastructure, migrating between SST versions, or need guidance on SST v3…