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 plangit 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/plan)<a href="https://agentmods.dev/skills/lisihao/solar/plan"><img src="https://agentmods.dev/badge/skills/lisihao/solar/plan/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/plan"><img src="https://agentmods.dev/badge/skills/lisihao/solar/plan.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.00015 | $0.00336 |
| Opus 5.5 | $0.00006 | $0.00134 |
| Sonnet 5.5 | $0.00003 | $0.00067 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
plan 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
Skill: plan
Turn user intent into a structured PRD, slice topology, and per-slice dispatch plan.
Trigger
User says: 写计划, 制定计划, /plan, Sprint planning
Steps
- Clarify intent — ask for outcomes, constraints, timeline if missing
- Draft PRD — Non-Negotiables, Target Architecture, Deliverables, Gates
- Slice topology — identify independent write scopes; draw dependency DAG
- Per-slice spec — Owner, Done conditions, Stop conditions, Round-retry trigger
- Gate checklist — G0..Gn with fail action
- Write plan.md — persisted to sprint directory
Output format
## 0. Slice Topology (DAG)
## 1. Slice Specs (S0..Sn)
## 2. Product Gates (table)
## 3. Risk Register
## 4. Rollback Plan
Done when
- plan.md passes schema gate (变更文件列表 + 技术方案 sections present)
- All slices have exclusive write scopes with no overlap
- Gate fail actions are specific (stop / rollback / no-release)
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 · 45 lines · 15 tokens per session scan A de57bde2899f
plan is a skill published in the GitHub repository lisihao/Solar (3 stars, last pushed 2mo ago), licensed MIT. It adds 15 tokens to every session and 336 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
openspec-bulk-archive-change
Archive multiple completed OpenSpec changes at once. Use when archiving several parallel changes. Also use for a plural archive request - "openspec bulk-archive", "opsx bulk-archive", "openspec archive all", or "openspec archive these changes".
openspec-archive-change
Archive a completed OpenSpec change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete. Also use when the user says "openspec archive" or "opsx archive".
kanban-board
A Kanban board is a visual task list with columns for stages such as To do, In progress, In review, and Done. It can show filters, labels, due dates, assignees, comments, and swimlanes that group cards.
write-prd
Write PRD — Product Requirements Documents with structured 8-section templates, user stories, acceptance criteria, and value proposition validation. Use when writing PRDs, defining product requirements, creating user stories with INVEST criteria, or building go/no-go decision frameworks.
mvp-plan
Plan the MVP build from a PRD and an MVP scope, as a full development plan or an ultra-lean build spec, with the AI Product Development Toolkit's planning prompts.
prd
Interview the owner about a product idea, then draft a Product Requirements Document (PRD) with the AI Product Development Toolkit's PRD prompt.