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 agentmods add skills/spideynolove/claude-dotfiles/sequential-thinkingnpx skills add spideynolove/claude-dotfiles --skill sequential-thinkinggit clone --depth 1 https://github.com/spideynolove/claude-dotfilesWrote 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/spideynolove/claude-dotfiles/sequential-thinking)<a href="https://agentmods.dev/skills/spideynolove/claude-dotfiles/sequential-thinking"><img src="https://agentmods.dev/badge/skills/spideynolove/claude-dotfiles/sequential-thinking.svg" alt="Measured on agentmods" 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 | $0.00032 | $0.02002 |
| Opus 5 | $0.00016 | $0.01001 |
| Sonnet 5 | $0.00006 | $0.00400 |
| Haiku 4.5 | $0.00003 | $0.00200 |
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.
How it starts
The opening of the file, as written. The whole thing — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sequential Thinking
Progressive disclosure framework for structured cognition and codebase analysis.
Core Principles
- Question-First: Define what you need to understand before using tools
- Reasoning Chains: Each thought explicitly depends on previous thoughts
- Cognitive Branches: Separate thinking tracks for different aspects
- Synthesis Before Action: Complete understanding before extraction
When to Use
- Analyzing new codebases
- Extracting reusable patterns
- Complex problem decomposition
- Building mental models
- Understanding domain-specific architectures
All 12 tools via mcporter
| Tool | Required params | Purpose |
|---|---|---|
start_session |
problem, success_criteria |
Begin a new thinking session |
add_thought |
content |
Add a thought to the current session |
create_branch |
name, from_thought, purpose |
Fork reasoning into a parallel track |
merge_branch |
branch_id |
Merge a branch back into main reasoning |
store_memory |
content |
Store a reusable insight |
query_memories |
(none) | Search memories by tags or content |
record_decision |
decision_title, context, options_considered, chosen_option, rationale, consequences |
Capture architecture decisions |
explore_packages |
task_description |
Find relevant installed packages |
export_session |
filename |
Export session or memories to file |
list_sessions |
(none) | List all saved sessions |
load_session |
session_id |
Resume a specific session |
analyze_session |
(none) | Get stats summary of current session |
Process
Phase 1: Problem Decomposition
# Check if session already loaded (server auto-loads last session on startup)
mcporter call sequential-thinking.analyze_session
# If no active session, start one
mcporter call sequential-thinking.start_session(
problem: "What fundamental questions must I answer?",
success_criteria: "Clear understanding of core questions",
session_type: "general"
)
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 · 287 lines · 32 tokens per session scan A 5b41f04c2458
sequential-thinking is a skill published in the GitHub repository spideynolove/claude-dotfiles (2 stars, last pushed 3mo ago), licensed MIT. It adds 32 tokens to every session and 2,002 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…