Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/biggora/claude-plugins-registry/delegate-bounded-worknpx skills add biggora/claude-plugins-registry --skill delegate-bounded-workgit clone --depth 1 https://github.com/biggora/claude-plugins-registryWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/biggora/claude-plugins-registry/delegate-bounded-work)<a href="https://agentmods.dev/skills/biggora/claude-plugins-registry/delegate-bounded-work"><img src="https://agentmods.dev/badge/skills/biggora/claude-plugins-registry/delegate-bounded-work.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00079 | $0.00853 |
| Opus 5 | $0.00039 | $0.00426 |
| Sonnet 5 | $0.00016 | $0.00171 |
| Haiku 4.5 | $0.00008 | $0.00085 |
Grade A, and why
delegate-bounded-work scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Delegate Bounded Work
Keep orchestration small, explicit, and evidence-driven. Retain end-to-end responsibility as the orchestrator.
Choose the Execution Mode
- Default to single-agent execution for a small coherent edit, a local investigation, or work whose context and verification already fit one agent. Avoid delegation when coordination cost exceeds its measurable benefit.
- Choose Mode 1: Bounded Delegation when one separable deliverable benefits from specialist knowledge, parallel discovery, context isolation, or a distinct tool surface.
- Choose Mode 2: Independent Fresh-Context Review when an existing artifact needs unbiased acceptance verification.
- State the chosen mode, the reason it adds value, assumptions, task boundary, and success evidence. Do not create a swarm to compensate for unclear scope.
Mode 1: Bounded Delegation
Delegate one atomic deliverable to one appropriate specialist. Keep dependent or cross-cutting integration with the orchestrator unless another boundary is independently verifiable.
Before dispatch, write a contract containing:
- Role: one specialized responsibility.
- Context: only repository and product facts needed for this deliverable.
- Task: exact actions, locations, and behavior.
- Constraints, tools, and authority: required skills/tools, quality rules, allowed mutations, and actions that require approval.
- Input: exact files, data, artifacts, or prior verified outputs.
- Expected output and acceptance criteria: deliverable format plus measurable proof.
- Example: one representative correct result or stable reference.
- Stop condition: completion boundary and conditions that require returning control rather than expanding scope.
Require the delegate to return the artifact or precise artifact location, a concise result summary, verification evidence, assumptions, and limitations. Do not request a full reasoning trace.
Inspect the result against every contract field. Grade it PASS, FAIL, or PARTIAL. Accept only PASS; for FAIL or PARTIAL, re-delegate with the failed criterion, observed evidence, and correction boundary instead of silently patching the delegate's work. Escalate a repeated identical blocker rather than adding agents or broadening authority.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 58 lines · 79 tokens per session scan A 8db5f3a12376
delegate-bounded-work is a skill published in the GitHub repository biggora/claude-plugins-registry (2 stars, last pushed 6d ago), licensed MIT. It adds 79 tokens to every session and 853 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…