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 antoinebou12/uml-mcp --skill sequential-thinkinggit clone --depth 1 https://github.com/antoinebou12/uml-mcpWrote 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/antoinebou12/uml-mcp/sequential-thinking)<a href="https://agentmods.dev/skills/antoinebou12/uml-mcp/sequential-thinking"><img src="https://agentmods.dev/badge/skills/antoinebou12/uml-mcp/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.1 | $0.00072 | $0.00610 |
| Opus 5 | $0.00036 | $0.00305 |
| Sonnet 5 | $0.00014 | $0.00122 |
| Haiku 4.5 | $0.00007 | $0.00061 |
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 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sequential Thinking
Break down complex work into ordered steps, revise when needed, and produce one clear answer. Use for multi-step tasks, planning, and problems where scope or approach may change.
When to Use
- Complex or multi-step tasks
- Planning and design with room for revision
- Analysis that might need course correction
- Problems where the full scope is unclear at the start
- Tasks that need context carried across steps
- When irrelevant information must be filtered out
- When the user asks for step-by-step reasoning
Behavior Without the MCP Tool
- Break the task into ordered steps.
- State one step at a time; build on the previous step.
- Revise earlier steps when you discover they are wrong or incomplete.
- Branch or backtrack when exploring alternatives.
- Generate a solution hypothesis when appropriate; verify it against the steps.
- Repeat until satisfied, then give a single, clear final answer.
Principles: Start with an estimate of how many steps you need and adjust as you go. Express uncertainty. Ignore information that is irrelevant to the current step.
Using the Sequential Thinking MCP Tool
When the sequentialthinking MCP tool is enabled (e.g. user-sequential-thinking server), prefer calling it for hard problems so thoughts are tracked and revisable.
- Required every call:
thought(current step),thoughtNumber,totalThoughts,nextThoughtNeeded. - Start with an initial estimate of
totalThoughts; increase or decrease as you progress. - Set
nextThoughtNeeded: trueuntil you are done; setnextThoughtNeeded: falseonly when you have a satisfactory final answer. - Revisions: Set
isRevision: trueandrevisesThoughtto the thought number you are reconsidering. - Branches: Use
branchFromThought(thought number) andbranchId(e.g. "alt-1") when exploring a different path. - More thoughts later: Set
needsMoreThoughts: truewhen you reach what seemed like the end but realize you need more steps.
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 · 52 lines · 72 tokens per session scan A bccc58119520
sequential-thinking is a skill published in the GitHub repository antoinebou12/uml-mcp (99 stars, last pushed 2d ago), licensed MIT. It adds 72 tokens to every session and 610 once invoked, about $0.0004 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-30.
Other skills, from other repositories
detailed-design
Skill for detailed design — class diagrams, sequence diagrams, API contracts, database schema design, and error handling strategy.
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment.
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.
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.