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 skills add Emlembow/skills --skill divisible-workgit clone --depth 1 https://github.com/Emlembow/skillsWrote 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/emlembow/skills/divisible-work)<a href="https://agentmods.dev/skills/emlembow/skills/divisible-work"><img src="https://agentmods.dev/badge/skills/emlembow/skills/divisible-work/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/emlembow/skills/divisible-work"><img src="https://agentmods.dev/badge/skills/emlembow/skills/divisible-work.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00155 | $0.03130 |
| Opus 5.5 | $0.00062 | $0.01252 |
| Sonnet 5.5 | $0.00031 | $0.00626 |
| Haiku 4.5 | $0.00015 | $0.00313 |
Grade A, and why
divisible-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 18d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Divisible Work
Own the path from the user's request to an accepted result. Keep that path adaptable: discover work, distribute useful pieces, accept evidence, and revise what should happen next.
The main thread coordinates only. Delegate substantive research, implementation, synthesis, repair, and verification. The coordinator may inspect context to plan, read results to make acceptance decisions, maintain records, manage workers, and communicate the delivered result. Do not take over substantive work merely because a worker is slow or a branch is indivisible.
Establish the run
- Apply this skill once at the user-task orchestration boundary. Workers under this coordinator execute their assignments; their assignment's complexity does not trigger another coordinator.
- Recover the requested outcome, acceptance criteria, destination, constraints, and existing authorization from context. Resolve discoverable facts and ask only for information necessary to proceed; continue independent work while an answer is pending.
- Inspect the host's actual chat creation, messaging, subagent, status, wait, and storage capabilities and current capacity. Prefer new worker Codex chats in the same project when host rules and human authorization permit. Use native subagents when chat delegation is unavailable, unauthorized, or prohibited. If the user explicitly forbids subagent fallback, report the limitation instead of substituting. A request to prefer chats alone does not forbid fallback. Do not invent worker IDs, availability, or background persistence.
- Require durable writable storage and a usable way to delegate and receive results. If either is unavailable, report the concrete limitation instead of silently executing locally. A temporarily occupied worker slot is waiting, not a missing capability.
- Before dispatch, read durable-state.md and create or resume
.divisible-work/<run-id>/in the task workspace, or the user's specified durable location. Announce the record location and initial path. Keep separate runs distinct; reuse an existing run only when it matches this task. - Record the outcome and acceptance criteria before decomposing. Fully specify the next actionable tasks; represent uncertain later stages as provisional milestones. Account for final integration and verification from the outset without pretending to know their detailed work yet.
What ships with it
4 files 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.
- 18d ago Changed · +12 lines · +35 tokens per session 7dc83141acfb
- 1mo ago Changed · +3 lines · +7 tokens per session 4a48508b5682
- 1mo ago First seen · 91 lines · 113 tokens per session scan A 5bb9e43068de
divisible-work is a skill published in the GitHub repository Emlembow/skills (2 stars, last pushed 18d ago), licensed MIT. It adds 155 tokens to every session and 3,130 once invoked, about $0.0006 per session on Opus 5.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-09-05.
Other skills, from other repositories
adversarial-spec
Iteratively refine a product spec by debating with multiple LLMs (GPT, Gemini, Grok, etc.) until all models agree. Use when user wants to write or refine a specification document using adversarial development.
prompt-master
Generates optimized prompts for AI tools. Activates only when the user explicitly asks to write, fix, improve, or adapt a prompt for a specific AI tool (LLM, Cursor, Midjourney, image AI, video AI, coding agents, etc.). Does not activate for general conversation, coding tasks, document writing, or other…
stuck
Diagnoses a broken course setup by reading the folder, so the student never has to describe the problem in English. Takes no argument. Reports which class they are on and which files are filled, then names one blocker and one fix: Claude Code opened at the wrong level, .claude/skills/ missing, skills not loading…
wrap-up
Saves today's work session as a four-line entry (did, decided, open, next) at the top of the project's log.md, after the student confirms it, so a fresh chat can continue tomorrow with /pick-up. Writes to projects/ /log.md or career-vault/log.md, one entry per project touched, never to new-client. Use when the student…
pick-up
Reads the newest entry of a project's log.md and tells the student where they left off: what they did and decided, what is open, and the next step. Takes an optional project name. With several projects and no name, shows a menu of each project's last entry. Read only. Use when the student says pick up, where did I…
grill-me
One move you can run on anything: point grill-me at a target and it makes you defend your thinking from first principles until the true matter is clear. Point it at your working contract and it rewrites the weak lines in place. Point it at a brief and it produces a Requirements Handshake. Point it at research, an…