A planning process for making a substantial change to a public open-source project before writing its code.

Use it when starting a feature or multi-file change, especially when external systems or unclear scope are involved.

It clarifies the smallest workable slice, order of work, checks, deployment path, trust boundaries, and risks to the public repository.

oss-plan — Skill for Claude Code by olgaiv39/claude-oss-skills

Install

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.

Any agent

npx skills add olgaiv39/claude-oss-skills --skill oss-plan

Clone the repo

git clone --depth 1 https://github.com/olgaiv39/claude-oss-skills

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/olgaiv39/claude-oss-skills/oss-plan/github.svg)](https://agentmods.dev/skills/olgaiv39/claude-oss-skills/oss-plan)

Your own site

<a href="https://agentmods.dev/skills/olgaiv39/claude-oss-skills/oss-plan"><img src="https://agentmods.dev/badge/skills/olgaiv39/claude-oss-skills/oss-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/olgaiv39/claude-oss-skills/oss-plan"><img src="https://agentmods.dev/badge/skills/olgaiv39/claude-oss-skills/oss-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 983 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00065	$0.00983
Opus 5.5	$0.00026	$0.00393
Sonnet 5.5	$0.00013	$0.00197
Haiku 4.5	$0.00006	$0.00098

Measured 2mo ago against content hash 2aeb11b18df1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

oss-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 2mo 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.

skills/oss-plan/SKILL.md · 128 lines

How it starts

The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.

oss-plan

Produce an execution plan that keeps the project runnable after every meaningful step. Do not write implementation code while using this skill.

Activate when

Starting a new feature or a non-trivial change
Scope, sequencing, or trust boundaries are unclear
A change will touch multiple files or an external system

Do not activate when

The change is a one-line fix with obvious validation -> use implement-minimal
The repository does not exist yet -> use oss-bootstrap
You are debugging a failure -> use test-and-debug

Required inputs

The feature or change request
Access to the repository to inspect status and conventions
Any external systems the feature must touch

Low-resource policy

Read the first of these that exists, then follow it:

${CLAUDE_PROJECT_DIR}/.claude/shared/LOW_RESOURCE.md
$HOME/.claude/shared/LOW_RESOURCE.md

If neither exists, apply this fallback: run one expensive command at a time, prefer the narrowest validation, disable watch mode, reuse existing environments, and run full validation only at a milestone boundary. Do not scan the whole filesystem to locate the policy.

Context-efficiency policy

Read the first of these that exists, then follow it:

${CLAUDE_PROJECT_DIR}/.claude/shared/CONTEXT_EFFICIENCY.md
$HOME/.claude/shared/CONTEXT_EFFICIENCY.md

If neither exists, apply this fallback: select files before reading; use targeted searches and bounded ranges; do not preload references; do not reread unchanged files; finish one atomic increment and stop; create a compact handoff before context is exhausted.

Facts that must not be assumed

The test runner, package manager, or build tool
That an external API, wallet, or MCP tool is available offline
That existing tests pass right now
The deployment target

Separate confirmed facts from assumptions and label every assumption.

Preflight

git status --short and git log --oneline -5 for current state
git diff --stat for uncommitted work in progress
Identify project conventions -> references/execution-planning.md
Identify external systems and trust boundaries -> references/trust-boundaries.md

Read the full file on GitHub · 128 lines

Files

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.

Changes

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.

2mo ago First seen · 128 lines · 65 tokens per session scan A 2aeb11b18df1

Subscribe to this mod's changes

oss-plan is a skill published in the GitHub repository olgaiv39/claude-oss-skills (13 stars, last pushed 3mo ago), licensed MIT. It adds 65 tokens to every session and 983 once invoked, about $0.0003 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.

Claude Code Planning agent-skills coding-agents deployment developer-productivity developer-tools

oss-plan next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
oss-planolgaiv39/claude-oss-skills	Skill	13	3mo ago	MIT	A	65	Claude Code
app-store-deploymakifbaysal/tasktrooper	Skill	122	yesterday	Apache-2.0	A	50	Claude Code, Codex
cloud-deploy-gcp-awsmakifbaysal/tasktrooper	Skill	122	yesterday	Apache-2.0	A	54	Claude Code, Codex
cdf-anomalygenNVIDIA/skills	Skill	4.0k	yesterday	Apache-2.0	A	54	Claude Code, Codex
jetson-diagnosticNVIDIA/skills	Skill	4.0k	yesterday	Apache-2.0	A	30	Claude Code, Codex
parabricksNVIDIA/skills	Skill	4.0k	yesterday	Apache-2.0	A	32	Claude Code, Codex
nemo-automodel-launcher-configNVIDIA/skills	Skill	4.0k	yesterday	Apache-2.0	A	30	Claude Code

oss-plan

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

oss-plan

Activate when

Do not activate when

Required inputs

Low-resource policy

Context-efficiency policy

Facts that must not be assumed

Preflight

What ships with it

What this file has done since we first saw it

oss-plan compared with skills from other repositories