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/dasdigitalemomentum/opencode-processing-skills/create-plannpx skills add DasDigitaleMomentum/opencode-processing-skills --skill create-plangit clone --depth 1 https://github.com/DasDigitaleMomentum/opencode-processing-skillsWhat 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.00036 | $0.02506 |
| Opus 5 | $0.00018 | $0.01253 |
| Sonnet 5 | $0.00007 | $0.00501 |
| Haiku 4.5 | $0.00004 | $0.00251 |
Grade A, and why
create-plan 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.
How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Create Plan
What This Skill Does
Creates a complete plan with the artifacts required to execute work in phases. This documentation shall serve Agents and Humans when working in consecutive sessions with the project:
- Plan (
plans/<name>/plan.md) - Problem/context, target outcome, guiding decisions, requirements, DoD, phases overview - Phases (
plans/<name>/phases/phase-N.md) - Scope definition per phase (what/why) - Todo List (
plans/<name>/todo.md) - Trackable items with status
This skill intentionally does not author per-phase implementation plans (plans/<name>/implementation/phase-N-impl.md).
Default next step (second pass): use author-and-verify-implementation-plan to author/verify the per-phase implementation plan against current repo reality.
When to Use
- When work is multi-phase or too large for a single session.
- When the user explicitly requests a persistent plan.
- When durable coordination or tracking is needed across agents, contributors, or sessions.
Do NOT use for a single bounded work package that can be gated with an inline brief containing its task, DoD, constraints, and final verification. Significance or non-triviality alone does not require plans/ persistence.
Execution Model (Recommended)
- Preferred: the primary agent runs this skill and writes artifacts under
plans/<name>/. - Rationale: plans are conversation-anchored (requirements, trade-offs, sequencing, DoD). Moving authorship to a subagent risks losing intent and introducing gaps.
- Read existing documentation first. Use
doc-exploreronly when bounded codebase impact/symbol analysis is necessary; do not create documentation merely to complete a plan template. - Optional (edge cases): use
doc-exploreronly to materialize/format a large set of plan files after the primary has finalized content and structure.
Routing Matrix (Who does what)
- Writes:
plans/<name>/plan.md,plans/<name>/phases/**,plans/<name>/todo.md, and creates directories underplans/<name>/. - Does NOT write:
plans/<name>/implementation/**(useauthor-and-verify-implementation-plan). - Primary: owns requirements, scope, DoD, phase breakdown, gating.
- doc-explorer: optional for repo-anchored analysis persisted into
docs/**and/or mechanical plan materialization. - implementer: never used for plan authoring.
What ships with it
3 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.
- 2d ago First seen · 181 lines · 36 tokens per session scan A 21c1019bd1b5
create-plan is a skill published in the GitHub repository DasDigitaleMomentum/opencode-processing-skills (59 stars, last pushed 22d ago), licensed MIT. It adds 36 tokens to every session and 2,506 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-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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.