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 rana/skills --skill phasegit clone --depth 1 https://github.com/rana/skillsWrote 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/rana/skills/phase)<a href="https://agentmods.dev/skills/rana/skills/phase"><img src="https://agentmods.dev/badge/skills/rana/skills/phase/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/rana/skills/phase"><img src="https://agentmods.dev/badge/skills/rana/skills/phase.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.00018 | $0.00372 |
| Opus 5.5 | $0.00007 | $0.00149 |
| Sonnet 5.5 | $0.00004 | $0.00074 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
phase 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.
What it actually says
Phase System
Research follows a sprint structure inspired by gstack. Each phase has distinct cognitive modes and exit criteria.
Phases
| Phase | Mode | Purpose | Exit Criteria |
|---|---|---|---|
| DREAM | Creative encounter | Generate hypotheses without judgment | 3+ hypotheses articulated |
| EXPLORE | Breadth search | Measure signals, map territory | Profiles computed, territory mapped |
| VALIDATE | Depth verification | Statistical gates, falsification | Walk-forward passes or finding recorded in RETURNED.md |
| IMPLEMENT | Direct action | Build what's validated | Code merged, tests passing |
| REFLECT | Meta-cognition | Update findings, prune returned | FINDINGS.md updated, session closed |
Current Phase Declaration
Declare the phase: $ARGUMENTS
If no phase specified, assess current state and recommend next phase based on:
- What's blocking (CONSTRUCTION-STATE.md)
- What's validated (FINDINGS.md)
- What's queued (RESEARCH.md)
Phase Transition Protocol
Before transitioning:
- Verify exit criteria of current phase are met
- Document what was learned in appropriate file
- Clear any blocking items or note them for next session
Output
- Current phase with timestamp
- Exit criteria for this phase instance
- Active question driving this phase
- Constraints (what's out of scope for this phase)
- Next phase (predicted, contingent on exit criteria)
Keep it short. The phase marker is a checkpoint, not a document.
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 · 46 lines · 18 tokens per session scan A ea079d8b6fcf
phase is a skill published in the GitHub repository rana/skills (1 stars, last pushed 6mo ago), licensed MIT. It adds 18 tokens to every session and 372 once invoked, about $0.0001 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 skills, from other repositories
decision
Single entry point for all decision operations: capture, search, manage. Routes based on natural language intent.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
pr-review
Comprehensive PR review across six dimensions — cost impact, environment drift, ownership gaps, SOC 2 compliance, deprecated API / version hygiene, and rollback feasibility. Each mode inspects the diff and current file state, reports findings with severity, and recommends concrete fixes. Use when preparing a PR for…
extract-resume
Parse a resume's uploaded PDF into structured JSON (basics, experience, projects, skills, education) and save it to the editor.
ensure-pipelines-host
Ensures the tenant has a usable Power Platform Pipelines host environment before any pipeline operation runs. Detects host state via the same resolution order as the Power Apps UI (org-db setting → BAP env metadata → default-custom-host setting); if any existing host (Platform or Custom) is found, uses it. If no host…
delegate
Let Claude Architect route a versioned implementation spec through the trusted MCP runtime, independently review the Candidate Artifact, record a decision, and integrate only accepted bytes. Use for implementation delegation, Producer selection, or commitment-boundary review.