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 siarhei-belavus/agent-public --skill split-initiativegit clone --depth 1 https://github.com/siarhei-belavus/agent-publicWrote 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/siarhei-belavus/agent-public/split-initiative)<a href="https://agentmods.dev/skills/siarhei-belavus/agent-public/split-initiative"><img src="https://agentmods.dev/badge/skills/siarhei-belavus/agent-public/split-initiative/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/siarhei-belavus/agent-public/split-initiative"><img src="https://agentmods.dev/badge/skills/siarhei-belavus/agent-public/split-initiative.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.00037 | $0.00494 |
| Opus 5 | $0.00018 | $0.00247 |
| Sonnet 5 | $0.00007 | $0.00099 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
split-initiative 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 10d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
split-initiative
Read first
../references/initiative-packet-contract.md../references/initiative-workflow-contract.md../references/final-state-authoring-policy.md- initiative
BRIEF.md,UBIQUITOUS_LANGUAGE.md,DECISIONS.md,INVARIANTS.md,REPO_MAP.md,CONTRACTS.md,OPEN_QUESTIONS.md - optional
SPLIT_OPTIONS.md ../../references/communication-mode.md
Goal
Write the first semantic TASK_GRAPH.md so each child is independently understandable, has explicit dependencies, and is small enough for a normal Atelier child loop.
Heuristics to internalize
- prefer vertical slices over horizontal phase buckets
- make each child understandable without giant hidden context
- state explicit scope, out-of-scope, validation expectations, and dependencies
- sequence by uncertainty and risk reduction
- keep one main change seam per child when possible
- prefer one clear owner repo per child; treat truly multi-repo children as a smell unless the boundary is genuinely inseparable
Write into TASK_GRAPH.md
For each child:
- slug / title
- owner or owning repo / boundary
Packet Root:repo root where the child packet will live- dependency edges
- scope summary
- contract surface summary
- validation expectations
- optional blocker note
Child Status: readywhen dependencies are already satisfied, otherwiseChild Status: pending
Status
- enter initiative
Status: split_draftingif no split-drafting phase already exists - exit with initiative
Status: split_review
Writing rule
Write the task graph as the canonical execution decomposition. Do not leave superseded split vocabulary or transitional child-state names in the graph.
Do not
- create giant catch-all children
- use the parent packet as a delivery plan
- reference outside Atelier skill files for split heuristics
Communication
Honor active caveman mode for user-facing replies per ../../references/communication-mode.md. Keep durable artifacts normal unless the human asks otherwise. Drop caveman for safety/clarity when needed, then resume.
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.
- 10d ago First seen · 54 lines · 37 tokens per session scan A a55ac584b2f2
split-initiative is a skill published in the GitHub repository siarhei-belavus/agent-public (2 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 494 once invoked, about $0.0002 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.