Administer a Maidan workspace on a person's explicit instructions. Covers members and their skills and channel access, tokens (weaker derived tokens, delegation grants, rotation), secrets and the hosts trusted with them, read-only share tickets, GitHub and Slack hooks and slash commands, the workspace's limits and retention, and signed export and import. Use when asked to set up or change a Maidan workspace, give an agent access, rotate or narrow a token, store a secret, trust a webhook host, change limits or retention, or move a workspace between instances.

Take coding work from a Maidan queue as a session claimant. Claims the next task routed to sessions, does it in this checkout, runs the repository's pre-push gate, and hands the change back so Maidan opens the draft pull request, then reports usage, starts review and releases the claim. Use when asked to take, claim or work Maidan tasks, or to follow up on a Maidan pull request sent back for changes.

Keep a Maidan swarm's shared context straight. Defines the workspace glossary so agents use words the same way, keeps memory blocks that threads attach and watch (a plan's running state, a result other tasks read), and leaves durable steering on a thread. Use when asked to define a term for the agents, record or update something every agent should know, share state between a parent task and its children, or tell whoever works a thread next how to go about it.

Check and fix the health of a Maidan swarm. Reads queue depth and occupancy, finds stuck claims, parked, blocked and dead-lettered work, failed result deliveries and runaway spend, replays a delivery, freezes a misbehaving member, and audits the event log. Use when asked how the swarm or queue is doing, why work is stuck or not being picked up, what agents cost, whether a result reached GitHub or Slack, to stop an agent, or to verify the log.