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 Haaaiawd/ANWS --skill sequential-thinkinggit clone --depth 1 https://github.com/Haaaiawd/ANWSWrote 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/haaaiawd/anws/sequential-thinking)<a href="https://agentmods.dev/skills/haaaiawd/anws/sequential-thinking"><img src="https://agentmods.dev/badge/skills/haaaiawd/anws/sequential-thinking/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/haaaiawd/anws/sequential-thinking"><img src="https://agentmods.dev/badge/skills/haaaiawd/anws/sequential-thinking.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.00046 | $0.02995 |
| Opus 5.5 | $0.00018 | $0.01198 |
| Sonnet 5.5 | $0.00009 | $0.00599 |
| Haiku 4.5 | $0.00005 | $0.00299 |
Grade A, and why
sequential-thinking 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sequential Thinking
这个 skill 的核心不是“多写几段 thought”，而是让 AI 在复杂问题里持续推进、允许修正，并最终收敛成结论。CLI 只是执行载体；skill 本身负责定义什么时候该进入这种思考方式，以及如何避免把顺序思考退化成松散输出。
Mission
这个 skill 用来把复杂问题处理成一个有边界、可修正、可复核的推理过程：
- 先澄清问题，而不是急着给答案
- 在推进过程中允许修正和调整判断
- 在复杂度上升时比较替代路径，而不是单线硬推
- 在有限步数内收敛成结论与建议
- 最后保留可回放的推理轨迹
它解决的不是“不会想”，而是“想得太散、太早下结论、太难复核”。
Core Capabilities
- 迭代推进: 把复杂问题拆成连续步骤，而不是试图一口气得到完整答案
- 动态修正: 当新证据出现时，允许回看并修正前面的判断
- 分支比较: 当存在替代路径时，允许先比较再收敛
- 上下文保持: 在多步推理中维持清晰的问题边界与目标
- 结论收束: 最终必须形成判断，而不是无限发散
When to Use
核心判断规则
模型能力决定基线，任务复杂度决定是否升级。
| 模型能力 | 简单任务 | 复杂任务 |
|---|---|---|
| 有思维链（CoT） | 自然 CoT 即可 | 调用 ST CLI |
| 无思维链 | 必须调用 ST CLI | 必须调用 ST CLI |
判断口诀
"无 CoT → 必须用 ST 有 CoT → 复杂才用 ST"
必须调用 CLI 的场景
| 场景 | 判断标准 | 为什么需要 CLI |
|---|---|---|
| 无 CoT 模型 | 当前模型不支持思维链输出 | 必须依赖外部工具组织推理 |
| 修正前提 | 推理过程中发现前面判断错了，需要回头修正 | CLI 会话保留历史，支持回看修正 |
| 多方案比较 | 需要在 2+ 个候选方案之间做权衡决策 | branch 模式专为分支比较设计 |
| 可回放轨迹 | 需要留下可审计、可复现的推理过程 | CLI 支持生成 replay 文档 |
| 复杂收敛 | 问题需要 > 5 步才能收敛到结论 | 强制步数限制防止无限发散 |
有 CoT 时可直接用自然 CoT 的场景
| 场景 | 判断标准 | 为什么不需要 CLI |
|---|---|---|
| 单向推理 | 不需要回头修正，线性推进 | 模型自然输出即可 |
| 简单分析 | 问题边界清晰、步骤 < 5 | 不需要复杂工具辅助 |
| 快速决策 | 只需结论，不需要可回放轨迹 | CoT 足够表达推理 |
| 探索性思考 | 还在发散阶段，不确定是否需要收敛 | 先用 CoT 探索，再决定是否用 CLI |
决策树
flowchart TD
A[需要多步推理?] -->|否| Z[直接回答]
A -->|是| B{模型有 CoT?}
B -->|否| CLI[必须调用 ST CLI]
B -->|是| C{任务复杂?}
C -->|简单: 步骤 < 5, 无修正| CoT[自然 CoT]
C -->|复杂: 修正/比较/回放| CLI
不适用场景
- 简单事实查询
- 单步即可完成的任务
- 路径已经非常明确、无需多步推演的问题
- 纯头脑风暴且暂时不要求收敛的场景
Working Philosophy
- 先找主问题，再找答案：不要把现象描述误当作根因定位
- 允许修正，而不是硬撑前提：前面想错了，就回头修，不要带着错误前提继续推进
- 先消除复杂度，再堆解决方案：优先识别主矛盾，而不是抢着给补丁
- 每一步只推进一步：当前步只表达当前判断，不重复整套背景
- 最终必须落到结论：不能把“我还能继续想”当作默认出口
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 · 223 lines · 46 tokens per session scan A 8d0f09464b8e
sequential-thinking is a skill published in the GitHub repository Haaaiawd/ANWS (141 stars, last pushed 5mo ago), licensed MIT. It adds 46 tokens to every session and 2,995 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
ai-engineering-toolkit
Overview of six AI engineering workflows: prompt evaluation (8-dimension scoring), context budget planning, RAG pipeline design, agent security audit (65-point checklist), eval harness building, and product sense coaching.
researcher
Delegate a deep research or survey task to Google's Antigravity CLI (agy staffer, fast Gemini). Use when the user says /agy:researcher, "ask agy to research", "have the agy staffer survey X", or wants a second, independent deep-dive on a topic or codebase without spending the host model's quota.
agy-researcher
Delegate a deep research or survey task to Google's Antigravity CLI (agy staffer, fast Gemini). Use when the user says /agy-researcher, "ask agy to research", "have the agy staffer survey X", or wants a second, independent deep-dive on a topic or codebase without spending the host model's quota.
reviewer
Get a second-opinion review from Google's Antigravity CLI (agy staffer, fast Gemini) - of code (a diff, PR, working tree) or of a decision, plan, or design. Use when the user says /agy:reviewer, "have agy review this", "second opinion on my diff/PR/plan", or after finishing work and wanting an independent verifier…
cancer-biologist
Think and work like an expert Cancer Biologist. Use when a task calls for Cancer Biologist judgment. Reasons from hallmark capabilities, clonal evolution, and TME context; separates driver from passenger, cell-autonomous from stromal mechanisms, and 2D artifacts from PDO/PDX-validated dependencies using TCGA, DepMap…
agronomist
Think and work like an expert Agronomist. Use when a task calls for Agronomist judgment. Reasons from 4R stewardship and G×E×M through MRTN economic N, calibrated soil-test extractants, penetrometer compaction diagnosis, on-farm strip mixed models, partial budgets, and AgroEcoList reporting while treating…