CordiaH

Haymarket Router — AI skill for Claude Code

AI community

AI Agent Router Designed to bridge the technical aspects of Web Development with the Organizational/Human aspects of running a business while minimizing token and resource usage.

How to install Haymarket Router

This entry records only its repository, not the path inside it, so there is no exact command to give. Open CordiaH/router and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Haymarket Router does

AI Agent Router Designed to bridge the technical aspects of Web Development with the Organizational/Human aspects of running a business while minimizing token and resource usage. Code is powered by Anthropic's Claude AI and Salesforce's Slack.

Alternatives in AI

Claude Task Master — by eyaltoledano - A task management system for AI-driven development with Claude, designed to work seamlessly 26k ★
Codeburn — Free, local tool to track AI coding token usage and cost across 37 tools and agents (Claude Code, Cursor, Code 9.7k ★
Ccstatusline — by sirmalloc - A highly customizable status line formatter for Claude Code CLI that displays model info, git b 5.5k ★

README

haymarket-router

Run a small team of Claude agents from Slack, with delegation that can't loop and deploys that can't ship without human sign-off.

**License:** MIT · **Status:** early, extracted from a real project · Node 22

What problem this solves

If you give several agents a Slack bot and let them mention each other, two things happen. They loop — each hop costing a full session's tokens — and somewhere in there one of them ships something nobody read.

This is the plumbing that prevents both. It came out of building [Haymarket Social](https://haymarket.social) with a Project Manager, a Coder, and an Editor, and it is MIT-licensed because none of it is specific to that project.

What it gives you

**One Slack app, many agent identities.** Distinct names and avatars per agent via `chat:write.customize`, so you don't register six Slack apps. Address them by prefix (`@bot coder: ...`) or by channel.

**Thread-scoped sessions.** One Slack thread maps to one Managed Agents session. Replying three hours later continues that session with full context — no re-mentioning, no re-pasting.

**A delegation queue instead of agent chatter.** Agents delegate through a tool call that enqueues a job, never by mentioning each other in a channel. Hop caps, cycle detection, and a per-agent allowlist are enforced in code, and the hop count travels with the request so it can't be reset by laundering a task through a third agent.

**A deploy gate with real approvals.** Configurable N-of-M agent sign-off before a beta deploy, then a human Block Kit button for production. Agents can't approve their own work — enforced by a database trigger, not a prompt. Promotion redeploys the exact reviewed SHA rather than whatever the branch head happens to be.

**An MCP server with per-agent tool scoping.** One bearer token per agent decides which tools that agent can see. An agent that shouldn't deploy never learns the tool exists, and calling it anyway is refused.