Borrowing it
Nothing to install: this file belongs to irahardianto/awesome-agv. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/irahardianto/awesome-agv/main/.agents/skills/sequential-thinking/SKILL.mdgit clone --depth 1 https://github.com/irahardianto/awesome-agvWrote 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/irahardianto/awesome-agv/sequential-thinking)<a href="https://agentmods.dev/skills/irahardianto/awesome-agv/sequential-thinking"><img src="https://agentmods.dev/badge/skills/irahardianto/awesome-agv/sequential-thinking.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00050 | $0.00957 |
| Opus 5 | $0.00025 | $0.00478 |
| Sonnet 5 | $0.00010 | $0.00191 |
| Haiku 4.5 | $0.00005 | $0.00096 |
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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- sequential-thinking — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sequential Thinking
A structured approach to complex problem-solving that breaks down challenges into iterative thought steps with built-in flexibility for revision and course correction.
When to Use This Skill
- Breaking down complex problems into manageable steps
- Planning and design requiring iterative refinement
- Analysis that might need course correction mid-stream
- Problems where the full scope emerges during analysis
- Multi-step solutions requiring context across steps
- Filtering out irrelevant information
- Hypothesis generation and verification workflows
Core Methodology
Sequential thinking follows a dynamic process:
- Initial estimation: Start with an estimate of thoughts needed, but remain flexible
- Iterative analysis: Work through thoughts sequentially while building context
- Revision capability: Question or revise previous thoughts as understanding deepens
- Branch exploration: Explore alternative approaches when needed
- Hypothesis cycle: Generate hypotheses, verify against thought chain, repeat
- Convergence: Continue until reaching a satisfactory solution
Instructions
Thought Structure
Each thought in the sequence should include:
- thought: Current thinking step content
- thoughtNumber: Position in sequence (1, 2, 3, ...)
- totalThoughts: Current estimate of total thoughts needed (adjustable)
- nextThoughtNeeded: Whether another thought step is required
Optional revision/branching metadata:
- isRevision: Boolean indicating if reconsidering previous thinking
- revisesThought: Which thought number is being revised
- branchFromThought: Branching point thought number
- branchId: Identifier for current branch
- needsMoreThoughts: Flag when reaching end but requiring more analysis
Process Guidelines
Starting out:
- Estimate initial thoughts needed based on problem complexity
- Begin with thought 1, establishing context and approach
- Set totalThoughts conservatively; you can adjust later
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 130 lines · 50 tokens per session scan A 9f716bc179f8
sequential-thinking is a skill published in the GitHub repository irahardianto/awesome-agv (156 stars, last pushed 17d ago), licensed MIT. It adds 50 tokens to every session and 957 once invoked, about $0.0003 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
agenttrace-session-audit
Audit local AI coding-agent sessions with agenttrace for cost, tool failures, latency, anomalies, health, diffs, and CI gates.
maintaining-windows-health
Hands-on playbook for Windows 11 disk cleanup, dev-machine optimization, and proactive health alerting. Use when the PC is full or slow, when a BSOD / Kernel-Power 41 / crash dump / commit-memory pressure happened, when the user asks to free disk space, audit storage, set up disk/memory alerts, or restore the same…
prompt-engineering
Universal prompt engineering techniques for any LLM. Use when crafting, optimizing, or reviewing prompts for AI models. Triggers on requests like "improve this prompt", "write a system prompt", "optimize my instructions", "help me prompt engineer", "audit this prompt", "review my prompt", or when building agentic…
installing-cli-tools
Install, upgrade, configure, and verify developer CLI tools safely. Use when a user asks to install a new CLI, command-line app, SDK tool, package-manager binary, GitHub release binary, language runtime tool, or AI/vendor CLI; configure shell PATH/completions; run first login; set API keys, tokens, or env variables…
repo-activity-summary
Summarize a repository's recent engineering activity from git history — technologies, work types, churn hotspots, contributor patterns, and velocity. Use when asking "what has this repo been working on", "is this project active", "who contributes what", "where are the hotspots", or before onboarding onto an unfamiliar…
eval-agents
Audit Claude Code agents defined in .claude/agents/ for description specificity, model tier appropriateness, tools scoping, and system prompt quality. Detects dispatch ambiguity between agents, flags over-permissive tool grants, and checks for human-in-the-loop patterns that break programmatic orchestration. Use when…