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 DasDigitaleMomentum/opencode-processing-skills --skill create-plangit clone --depth 1 https://github.com/DasDigitaleMomentum/opencode-processing-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/dasdigitalemomentum/opencode-processing-skills/create-plan)<a href="https://agentmods.dev/skills/dasdigitalemomentum/opencode-processing-skills/create-plan"><img src="https://agentmods.dev/badge/skills/dasdigitalemomentum/opencode-processing-skills/create-plan/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/dasdigitalemomentum/opencode-processing-skills/create-plan"><img src="https://agentmods.dev/badge/skills/dasdigitalemomentum/opencode-processing-skills/create-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 73 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00036 | $0.02304 |
| Opus 5.5 | $0.00014 | $0.00922 |
| Sonnet 5.5 | $0.00007 | $0.00461 |
| Haiku 4.5 | $0.00004 | $0.00230 |
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 1mo 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 — 177 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.
- 1mo ago Changed · -4 lines fe7cb4ddd406
- 1mo 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 (60 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 2,304 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
duckduckgo-search
Free keyless web, news, and image search via ddgs.
mcporter
List, auth, and call MCP servers/tools from the terminal.
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
safe-refactor
Restructure code while preserving behavior. Use for extraction, consolidation, ownership moves, or cleanup where verification must bracket structural edits.