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 lisihao/Solar --skill phasegit clone --depth 1 https://github.com/lisihao/SolarWrote 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/lisihao/solar/phase)<a href="https://agentmods.dev/skills/lisihao/solar/phase"><img src="https://agentmods.dev/badge/skills/lisihao/solar/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/lisihao/solar/phase"><img src="https://agentmods.dev/badge/skills/lisihao/solar/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.00008 | $0.01178 |
| Opus 5 | $0.00004 | $0.00589 |
| Sonnet 5 | $0.00002 | $0.00236 |
| Haiku 4.5 | $0.00001 | $0.00118 |
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 7d 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/phase - 阶段转换
命令
| 命令 | 说明 |
|---|---|
/phase next |
转换到下一阶段 |
/phase P1-P5 |
跳转到指定阶段 |
/phase status |
显示当前阶段 |
执行流程
/phase next
必须按以下步骤执行:
1. 读取当前状态
读取 .solar/flow-state.json，获取当前阶段。
2. 确定下一阶段
| 当前 | 下一 | 条件 |
|---|---|---|
| P1 | P2 | 研究完成 |
| P2 | P3 | G1 Gate (设计文档) |
| P3 | P4 | 代码完成 |
| P4 | P5 | G2 Gate (测试通过) |
| P5 | 完成 | 收尾工作完成 |
3. 执行 Gate 检查 (如需要)
P2 → P3 (G1 Gate):
- 检查是否有设计文档
- 失败可重试 2 次
P4 → P5 (G2 Gate):
- 检查测试是否通过
- 失败可重试 3 次
4. 更新状态文件
{
"flow": {
"current_phase": "<新阶段>",
"current_agent": "<新Agent>"
},
"agent_announcement": {
"announced": false
}
}
5. 输出转换信息
┌─ ☀️ Solar 阶段转换 ─────────────────────────────┐
│ <旧阶段> <旧Agent> → <新阶段> <新Agent> │
├─────────────────────────────────────────────────┤
│ 新阶段: <阶段名> │
│ Agent: <emoji> <Agent名> │
│ 职责: <Agent职责描述> │
└─────────────────────────────────────────────────┘
6. 输出新 Agent 宣告
必须立即输出新 Agent 的宣告框:
┌─ <emoji> <Agent名> ─────────────────────────────┐
│ Task: <继承自上一阶段的任务目标> │
│ Plan: │
│ 1. <本阶段步骤1> │
│ 2. <本阶段步骤2> │
└─────────────────────────────────────────────────┘
7. 更新宣告状态
"agent_announcement": {
"announced": true
}
/phase P1-P5 (跳转)
允许跳转到指定阶段，但会显示警告:
⚠️ 跳转到 <阶段>，跳过了 Gate 检查。
然后执行与 /phase next 相同的步骤 4-7。
阶段详情
P1 研究 (Researcher 🔬)
职责: 技术调研、可行性分析 产出: 研究报告 工具限制: 禁止 Edit, Bash
P2 设计 (Architect 🏗️)
职责: 架构设计、方案评审 产出: 设计文档 (docs/*_DESIGN.md) 工具限制: 禁止执行命令 (只读命令除外)
P3 实现 (Coder 💻)
职责: 代码实现、重构 产出: 代码文件 工具限制: 无
P4 验证 (Tester 🧪)
职责: 测试编写、执行 产出: 测试报告 工具限制: 无
P5 收尾 (Ops ⚙️)
职责: 构建、部署、文档 产出: 部署完成、文档更新 工具限制: 无
Gate 检查
G1 Gate (P2 → P3)
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.
- 7d ago First seen · 173 lines · 8 tokens per session scan A 05bdaaec6c67
phase is a skill published in the GitHub repository lisihao/Solar (2 stars, last pushed 28d ago), licensed MIT. It adds 8 tokens to every session and 1,178 once invoked, about $0.0000 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.