Yannickloth Claude Router System
- Updated February 16, 2026
- yannickloth/claude-router-system
yannickloth-claude-router-system is a Claude Code plugin that provides an IVP-architecture router for intelligent agent delegation and cost-aware request routing.
About
yannickloth-claude-router-system is a Claude Code plugin that implements a reusable routing layer with IVP-style architecture: a central coordinator assesses incoming work, delegates to specialized agents, and aims to optimize cost across your subscription and model mix. developers who run Claude Code as their primary IDE often hit the same wall—every task feels like it should go to the strongest model, context balloons, and simple edits pay premium prices. This plugin treats routing as first-class agent tooling you set up once and reuse across Idea research, Validate spikes, Build implementation, Ship checks, and ongoing Operate maintenance. Complexity assessment and intelligent delegation are the core promises: general requests get triaged, specialized paths handle narrow jobs, and the system stays IVP-compliant as described in the upstream project. It is infrastructure, not a feature skill—install when you want a deliberate orchestration pattern instead of ad-hoc subagent prompts in every session.
- Reusable Claude Code router with IVP (intelligent delegation) architecture
- Routes general requests through specialized agents based on complexity assessment
- Cost and subscription-aware optimization for agent delegation
- Central entry point so one system coordinates multiple downstream agents
- Single-plugin bundle focused on routing and architecture (plugin count 1)
Yannickloth Claude Router System by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin install yannickloth-claude-router-system@yannickloth/claude-router-systemAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| Last updated | February 16, 2026 |
|---|---|
| Repository | yannickloth/claude-router-system ↗ |
What it does
Install a central Claude Code router that delegates requests to specialized agents under IVP rules and trims token spend.
Who is it for?
Power users running Claude Code daily who want structured multi-agent delegation and subscription-conscious routing.
Skip if: Casual users who only run short single-turn edits and do not want to maintain routing configuration.
What you get
You get a central routing system that assesses complexity, delegates to specialized agents, and keeps Claude Code usage closer to your cost and architecture rules.
- Configurable central router for Claude Code sessions
- Complexity-based paths to specialized agents
- Reusable IVP-compliant routing pattern for multiple projects
Recommended Plugins
0pg Cc MarketplacePersonal Claude Code plugins collection
1shot Labs Squadron Comms PluginVoice communication system with ElevenLabs TTS for multi-agent coordination in Claude Code3
23blocks Os Ai MaestroAI Agent Orchestrator with Skills System - Give AI Agents superpowers: memory search, code graph queries, agent-to-agent messaging.733
3commas Io Commas ClaudeThis is a repo with shared agents and skills used company-wide4
884js Agent Plugins1 plugin
A5c Ai BabysitterBabysitter enforces obedience to agentic workforces and enables them to manage extremely complex tasks and workflows through deterministic, hallucination-free self-orchestration1.6kHow it compares
Agent orchestration router plugin, not a single-task MCP integration or skills.sh marketplace listing.
FAQ
Who is Yannickloth Claude Router System for?
It is for Claude Code operators who want IVP-style central routing, specialized agent delegation, and cost optimization across many types of requests.
When should I use Yannickloth Claude Router System?
Use it when you are setting up or scaling agent-tooling and need consistent routing from idea research through ship and operate workflows.
How do I add Yannickloth Claude Router System to my agent?
Install the plugin in Claude Code, configure the router and delegate agents per the IVP architecture docs in the repository, then route sessions through the central entry point.