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 mcp/xvirobotics/metaskill/data-science-sequential-thinkinggit clone --depth 1 https://github.com/xvirobotics/metaskillWrote 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/mcp/xvirobotics/metaskill/data-science-sequential-thinking)<a href="https://agentmods.dev/mcp/xvirobotics/metaskill/data-science-sequential-thinking"><img src="https://agentmods.dev/badge/mcp/xvirobotics/metaskill/data-science-sequential-thinking.svg" alt="Measured on agentmods" height="20"></a>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 3d 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.
This is a copy
88% identical to sequential-thinking — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"sequential-thinking": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-sequential-thinking"
],
"env": {}
}
}What else .mcp.json configures
This page is one entry in a file that holds 3. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 3d ago First seen · 10 lines scan A 0742b11ce15b
sequential-thinking is an MCP server published in the GitHub repository xvirobotics/metaskill (67 stars, last pushed 6mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. It is 88% identical to sequential-thinking, differing in 3 lines, and is treated as a copy.
Other mcp servers, from other repositories
sequential-thinking
Adds a structured step-by-step reasoning tool the agent can call to break a problem into revisable thoughts. Runs locally from the @modelcontextprotocol/server-sequential-thinking npm package.
context7
Gives the agent up-to-date documentation and code examples for libraries and frameworks, fetched on demand so answers are not stuck at the model's training cutoff. Runs locally from the @upstash/context7-mcp npm package.
memory
Gives the agent a persistent knowledge graph it can write facts to and recall across sessions. Runs locally from the @modelcontextprotocol/server-memory npm package.
claude-octopus
Spawn multiple specialized Claude Code agents as MCP servers, each independently configured. Runs locally from the claude-octopus npm package. Needs 7 environment variables to run.
work-buddy
MCP server "work-buddy", hosted remotely at localhost, as configured in KadenMc/work-buddy.
agent-bus
MCP server "agent-bus" as configured in MustaphaSteph/agent-bus-plugins. Launched with agent-bus-mcp.