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 markerikson/opencode-config-example --skill development-plangit clone --depth 1 https://github.com/markerikson/opencode-config-exampleWrote 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/markerikson/opencode-config-example/development-plan)<a href="https://agentmods.dev/skills/markerikson/opencode-config-example/development-plan"><img src="https://agentmods.dev/badge/skills/markerikson/opencode-config-example/development-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/markerikson/opencode-config-example/development-plan"><img src="https://agentmods.dev/badge/skills/markerikson/opencode-config-example/development-plan.svg" alt="Reviewed on agentmods" width="80" 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.00039 | $0.01917 |
| Opus 5.5 | $0.00016 | $0.00767 |
| Sonnet 5.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 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 — 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.
- 1mo 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 (48 stars, last pushed 5mo ago), licensed MIT. It adds 39 tokens to every session and 1,917 once invoked, about $0.0002 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…