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/resume-plannpx skills add DasDigitaleMomentum/opencode-processing-skills --skill resume-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/resume-plan)<a href="https://agentmods.dev/skills/dasdigitalemomentum/opencode-processing-skills/resume-plan"><img src="https://agentmods.dev/badge/skills/dasdigitalemomentum/opencode-processing-skills/resume-plan.svg" alt="Measured on agentmods" 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.00048 | $0.01713 |
| Opus 5 | $0.00024 | $0.00856 |
| Sonnet 5 | $0.00010 | $0.00343 |
| Haiku 4.5 | $0.00005 | $0.00171 |
Grade A, and why
resume-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 5d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Resume Plan
What This Skill Does
Bridges the gap between planning artifacts and implementation. When a new session starts and the agent needs to continue work on an existing plan, this skill:
- Finds the active plan and identifies the current phase
- Reads all relevant artifacts in the correct order (context bootstrap)
- Validates that prerequisites for the current phase are met
- Presents a concise briefing to the agent/user: what to do, where to look, what was decided
- Prepares the todo list as the working entry point
Why This Skill Exists
Planning skills (create-plan, update-plan) produce artifacts. Implementation happens across sessions. Without a defined bootstrap procedure, every new session starts with ad-hoc exploration -- the agent must independently discover which plan exists, which phase is active, what was decided, and what files to read. This wastes context budget and risks missing critical decisions from prior sessions.
This skill codifies the read-path that complements the write-path of the other planning skills.
When to Use
- At the start of a new session when continuing a multi-session plan
- When the user says "continue with the plan", "resume phase N", or "what's next"
- After a session handover was created in a previous session
- When onboarding a different agent to an existing plan
Do NOT use this skill to create or modify plans -- use create-plan or update-plan instead.
Execution Model
- Always: the primary agent runs this skill directly.
- Rationale: session bootstrap is fundamentally a context-building activity. The primary needs the context to guide the implementation session. Delegating to a subagent would build context in the wrong place.
- Use
doc-explorer: optionally, to validate prerequisites that require codebase inspection (e.g., "Phase 1 tests must pass"). Results are written todocs/, not returned as text. - Do NOT delegate to
doc-explorer: this skill reads artifacts, it does not write them.
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.
- 5d ago First seen · 138 lines · 48 tokens per session scan A 71582750cc11
resume-plan is a skill published in the GitHub repository DasDigitaleMomentum/opencode-processing-skills (58 stars, last pushed 26d ago), licensed MIT. It adds 48 tokens to every session and 1,713 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…