worker-ceiling

Enforces worker-tier and agent-count caps in sub-agent dispatch harnesses.

Updated May 11, 2026

Search Tags:#optimization #dispatch #efficiency #cost control #sub-agent #harness

Ready to run

npx skills add https://github.com/AesopScott/mojo --skill worker-ceiling

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: worker-ceiling
Source: https://github.com/AesopScott/mojo/tree/main/harnesses/skills/worker-ceiling
Command: npx skills add https://github.com/AesopScott/mojo --skill worker-ceiling

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses runaway costs and resource waste in sub-agent dispatch systems by providing a structured framework to enforce operational boundaries.

Core Features & Use Cases

Cost Control: Implements per-stage worker-model tiering and agent-count caps to prevent excessive token or compute usage.
Efficiency Optimization: Enables early-exit logic for empty stages to minimize unnecessary processing.
Use Case: When a sub-agent dispatch process is exceeding budget, use this Skill to define a strict worker-model tier and agent-count ceiling to immediately bound the spend.

Quick Start

Use the worker-ceiling skill to inspect the current sub-agent dispatch configuration and propose a cost-limiting patch plan.

Frequently Asked Questions about worker-ceiling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I control sub-agent dispatch costs in complex agentic workflows?▼

To control sub-agent dispatch costs, you enforce per-stage worker-model tiering and agent-count caps, bounding compute and token usage within the dispatch harness to prevent excessive spending.

What is the best way to limit token usage during multi-agent dispatch execution?▼

The best way to limit token usage is by applying a worker-model tier ceiling to the dispatch process, immediately bounding spend and enforcing strict operational safety boundaries across stages.

How does early-exit logic improve dispatch efficiency in sub-agent harnesses?▼

Early-exit logic improves dispatch efficiency by detecting empty stages and bypassing unnecessary processing, minimizing wasted compute and ensuring the sub-agent harness only executes when required.

Why does my sub-agent dispatch process keep exceeding the compute budget?▼

Your sub-agent dispatch process exceeds the compute budget because it lacks strict control levers, requiring defined worker-model tiers and agent-count ceilings to bound the spend and verify execution.

Can I apply agent-count caps to specific stages in an agentic workflow?▼

Yes, you can apply agent-count caps to specific stages, enforcing resource constraints and operational safety by defining control levers that limit the number of agents executing per stage.

When do I need a worker-ceiling framework for sub-agent dispatch?▼

You need a worker-ceiling framework when a sub-agent dispatch process is exceeding budget, requiring strict control over worker-model tiers and bounded compute to prevent runaway operational costs.