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/markerikson/opencode-config-example/development-plannpx skills add markerikson/opencode-config-example --skill development-plangit clone --depth 1 https://github.com/markerikson/opencode-config-exampleWhat 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.00039 | $0.01917 |
| Opus 5 | $0.00019 | $0.00958 |
| Sonnet 5 | $0.00008 | $0.00383 |
| Haiku 4.5 | $0.00004 | $0.00192 |
Grade A, and why
development-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 — 323 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development Plan Skill
Create detailed, actionable development plans that serve as living documents for tracking multi-phase project execution.
When to Use This Skill
- Multi-week projects with multiple phases
- Work requiring detailed task breakdown
- Projects needing progress tracking over time
- Complex migrations or refactors
- When you need to track "what we learned" alongside tasks
Don't use for:
- Single-session work (use simple work doc from
/new-work) - Small features (< 3 days)
- Exploratory work without clear tasks yet
Document Template
Title and Metadata
# [Project Name] Development Plan & Progress Tracker
**Document Purpose:** This is a living document that tracks the overall development plan, task lists, and progress for [brief description].
**Last Updated:** YYYY-MM-DD
---
Section 1: Document Purpose
Explicitly state what this document tracks.
## Document Purpose
This document serves as the central hub for:
- **Overall Development Plan:** Breaking [work] into logical phases
- **Task Lists:** Detailed, actionable tasks for each phase
- **Progress Tracking:** What's done, what's in progress, what's remaining
- **Notes & Learnings:** Capturing insights, decisions, and discoveries
- **Open Questions:** Items requiring further investigation
This is a **living document** that will be updated frequently as we:
- Complete tasks and mark them done
- Discover new work that needs to be added
- Learn patterns and make design decisions
- Encounter and solve challenges
Section 2: Key Constraints (Optional but Recommended)
Critical scope limitations that need constant visibility.
## Key Constraints
> **⚠️ SCOPE:** [Critical constraint that affects all work]
>
> - NOT doing [thing]
> - NOT supporting [thing]
> - This is [approach/limitation]
Section 3: Phase Overview
High-level summary of all phases (1-2 sentences each).
## Phase Overview
The [work] is organized into [N] major phases:
### Phase 1: [Name]
**Goal:** [One sentence goal]
**Key Activities:** [3-5 bullets of major work]
### Phase 2: [Name]
...
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 · 323 lines · 39 tokens per session scan A fdb739d37800
development-plan is a skill published in the GitHub repository markerikson/opencode-config-example (44 stars, last pushed 3mo ago), licensed MIT. It adds 39 tokens to every session and 1,917 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
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.
a-evolve
Apply A-Evolve's agentic evolution methodology to improve AI agent performance across runs. Use when the user wants to diagnose agent failures, generate targeted skills from error patterns, evolve system prompts, or accumulate episodic knowledge. Works standalone or inside AutoResearchClaw pipelines. Triggers on…
hive.chart-creation-foundations
Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…
📝 任务完成后归档
重要提醒: 每次完成复杂调试或开发任务后，主动执行此流程！ 将学到的经验归档为 skill，供以后参考。不要等用户提醒。.
deck-course-module
暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.
code-documenter
Use when adding docstrings, creating API documentation, or building documentation sites. Invoke for OpenAPI/Swagger specs, JSDoc, doc portals, tutorials, user guides.