team vs Pathrule
team is no longer listed on any marketplace we read: these are its last known data, as of 2026‑11‑01.
team is a plugin bundle for AI coding tools published by dstoic. No marketplace we read lists it any more. Pathrule is an MCP server published by pathrule.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-05. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Pathrule | |
|---|---|---|
| Community marketplace digital-stoic-org/agent-skills | Removed on 2026-11-01 Version: 0.9.0 Forks (GitHub): 7 Stars (GitHub): 21 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed, marked deprecated Version: 0.1.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | teamno longer listed · | Pathrule |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 21 | No figure on GitHub |
| Forks (GitHub) (differs) | 7 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp.pathrule.io/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 3 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/digital-stoic-org/agent-skills | github.com/sertanhelvaci/pathrule |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-16 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 32 h ago returned HTTP 308 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of team
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Hook-driven state machine for orchestrating a three-agent Claude feature team
-
Allowing the agents of the same user or of the user teams to communicate between themselves while they are executing tasks. Imagine Slack, but for Claude agents.
-
Multi-agent team bootstrapper and runtime orchestrator — generates tailored agent teams via AI debate and runs parallel team patterns (review, debate, plan, build, research)
-
A modular plugin that packs specialised agents into teams and allows user to interact with them at the higher level of abstraction. Like with real-world company departments.
-
AI Agent Team Operating System for Claude Code. Provides persistent team management, meeting collaboration, task wall with pipeline workflows, company loop engine, and 79 MCP…
-
Multi-agent team orchestration for Claude Code (Chinese)
What each says it does
team
Coordination protocol for running a fleet of named Claude Code agents in parallel under one human: delegate one mandate at a time (brief), report back on a stop condition (report), hand off state at context limits (relay) — one skill per machine arrow, SendMessage the only transport. No skill reads the protocol at runtime: the mandate carries its own contract, so all three run in windows with no context to spare without reading anything at all, and a window that has never seen the plugin still behaves correctly. Context is under the human's control on both sides: read_first closes what a delegate opens before it starts, deliverable puts its findings on disk so reports and relay packets carry pointers rather than content, and a relay hands its successor the role lines that land it in READY instead of straight back into the work.
Pathrule
Path-scoped team memories, rules and skills for Claude Code, Cursor, Codex and other MCP clients.
How to run each
team
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Pathrule As a remote MCP server
claude mcp add --transport http pathrule-remote-mcp https://mcp.pathrule.io/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Pathrule has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: team · What it can do: Pathrule · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.