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/retz8/pastiche/divide-tasknpx skills add retz8/pastiche --skill divide-taskgit clone --depth 1 https://github.com/retz8/pasticheWhat 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.00060 | $0.00481 |
| Opus 5 | $0.00030 | $0.00241 |
| Sonnet 5 | $0.00012 | $0.00096 |
| Haiku 4.5 | $0.00006 | $0.00048 |
Grade A, and why
divide-task 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 2d 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.
What it actually says
divide-task
Harness conventions: _dev/docs/harness.md. Requires: task spec written, task [WIP], feature branch checked out.
Workflow
-
Derive sub-tasks from the spec. Each sub-task is one implementation step, sized for a single overnight session. Number them
N.1, N.2, …whereNis the task's TODO number. -
Analyze each sub-task:
- Autonomy — purely mechanical, mergeable without human judgment →
autonomous-ready; otherwise →decision-needed. When in doubt,decision-needed. - Dependencies — which sub-tasks must land first. Independent sub-tasks that touch disjoint files/logic may run in parallel; note the execution order.
- Autonomy — purely mechanical, mergeable without human judgment →
-
Review with the user before creating anything: list sub-tasks, labels, and dependency order. Adjust until approved.
-
Create child issues. For each sub-task:
- Title
[N.x] <name>; body: one-paragraph scope + pointer to the spec path; same milestone as the parent; autonomy label. - For blocked ones: create
blocked-by-<blocker-issue-number>labels on demand (gh label create) and apply them. Blockers must be created first so their issue numbers exist. - Link each as a sub-issue of the parent (GitHub sub-issue, or a task-list in the parent body if unavailable).
- Title
-
Mirror into
_dev/TODO.md. Under the task line, add an indented checklist:- [ ] **N.x** <name> (#<issue>). -
Update the parent issue. Add the sub-issue links and the spec reference.
Label lifecycle (for whoever completes a sub-task)
When a blocking sub-task closes, remove its blocked-by-<its-number> label from every issue carrying it, and tick the sub-task checkbox in TODO.md.
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.
- 2d ago First seen · 32 lines · 60 tokens per session scan A d2a8ac79bc73
divide-task is a skill published in the GitHub repository retz8/pastiche (4 stars, last pushed 2mo ago), licensed MIT. It adds 60 tokens to every session and 481 once invoked, about $0.0003 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
material-ui-styling
Chooses the right Material UI styling approach (sx, styled, theme overrides, global CSS) from official MUI guidance. Use when styling @mui/material components, customizing themes, overriding slots, or comparing sx vs styled.
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
fast-typescript-check
Keep www-sacred's TypeScript fast to type-check and fast to run. Use when touching the ASCII/canvas animation components (the only real per-frame code here), tightening type-check wall-clock, or auditing a change for runtime or compiler regressions. Scoped to this repo — a React 19 / Next.js 16 component library plus…
snapshot-release
Drives the snapshot-release flow for the current branch's PR. Posts a /snapshot comment on the PR if one isn't already there (with confirmation), waits for the Continuous Releases workflow to finish, and reports the tarball URLs from the resulting 📦 Snapshot Release comment. Use for both triggering and waiting …
survey-design
Design unbiased survey instruments — question wording, scales, and sampling — to measure attitudes at scale. Use when you need quantitative breadth. For behavioural experiments, use a-b-test-design (prototyping-testing).
ss-score
Score a visual artifact's implementation quality 0-100 against its composed StyleSeed rule set — category breakdown, evidence, and prioritized fixes.