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/djscheuf/agentic-dev-ecosystem-template/split-plan-into-workstreamsnpx skills add djscheuf/agentic-dev-ecosystem-template --skill split-plan-into-workstreamsgit clone --depth 1 https://github.com/djscheuf/agentic-dev-ecosystem-templateWhat 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.00020 | $0.00763 |
| Opus 5 | $0.00010 | $0.00381 |
| Sonnet 5 | $0.00004 | $0.00153 |
| Haiku 4.5 | $0.00002 | $0.00076 |
Grade A, and why
split-plan-into-workstreams 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 3d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Steps:
1. Read the Story Analysis Document
- Read the story analysis json document.
2. Read the Draft Implementation Plan
- Read the draft implementation plan json document.
3: Identify Work Streams
Break the work into parallel tracks:
TYPICAL WORK STREAMS:
├── Foundations
│ ├── Contracts and Interfaces Defined
│ ├── Database migrations
│ ├── Data model changes
│ ├── API endpoint Stubbed with fake response data
│ └── Frontend API calls to stubbed endpoints
├── Backend/API
│ ├── Repositories, and Handlers
│ ├── Business logic
│ └── API endpoints fully built
├── Frontend/UI
│ ├── Components
│ ├── State management
│ └── Completed API integration
├── Infrastructure
│ ├── Configuration
│ └── Deployment
└── Testing
├── Integration tests
└── E2E tests
The Foundations workstreams purpose is to enable parallel development of the rest of the feature.
5. Create Workstream Directories
Create a subdirectory streams under the same folder that contains the story analysis and plan json documents.
5. Create Workstreams
For each workstream, complete the following steps.
5.1 Create Workstream Document
Create a workstream json document. The workstream document will follow the schema in schema/workstream.schema.json. The document should be named {workstream-name}.stream.json and placed under the streams subdirectory.
5.1 Identify Stream-related Criteria
Copy the Acceptance Criteria and Edge Cases from the analysis document that are related to the workstream's scope to the "related_acceptance_criteria" and "related_edge_cases" fields in the workstream json document.
5.2 Identify Stream Dependencies
Identify any dependencies that the workstream has on other workstreams. Update the "dependencies" field in the workstream json file. Dependencies can include completion of other workstreams, or specific artifacts from other workstreams.
5.3 Outline Stream Implementation Plan
Outline high-level approach:
IMPLEMENTATION PLAN:
1. [First major step]
2. [Second major step]
3. [Third major step]
...
And for each step identify what artifacts are needed to complete the step.
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.
- 3d ago First seen · 93 lines · 20 tokens per session scan A c7ef8d61525d
split-plan-into-workstreams is a skill published in the GitHub repository djscheuf/agentic-dev-ecosystem-template (12 stars, last pushed 3d ago), licensed MIT. It adds 20 tokens to every session and 763 once invoked, about $0.0001 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…