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 olgaiv39/claude-oss-skills --skill oss-plangit clone --depth 1 https://github.com/olgaiv39/claude-oss-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/olgaiv39/claude-oss-skills/oss-plan)<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.
<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>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 | $0.00032 | $0.00491 |
| Sonnet 5 | $0.00013 | $0.00197 |
| Haiku 4.5 | $0.00006 | $0.00098 |
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 11d 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 — 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 --shortandgit log --oneline -5for current stategit diff --statfor uncommitted work in progress- Identify project conventions -> references/execution-planning.md
- Identify external systems and trust boundaries -> references/trust-boundaries.md
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.
- 11d ago First seen · 128 lines · 65 tokens per session scan A 2aeb11b18df1
oss-plan is a skill published in the GitHub repository olgaiv39/claude-oss-skills (12 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 983 once invoked, about $0.0003 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
projectatlas
Use ProjectAtlas as the atlas-first orientation layer before broad source reads, with MCP-first task startup, short-alias worktree registration and routing, safe targeted initialization, ranked navigation, exact or federated graph evidence, purpose curation, health, lint, and repository-wide token reporting.
codex-coding-plugin
Build, review, or fix ProjectAtlas plugin/runtime installer integration for Codex, Claude Code, and OpenCode, especially version convergence, stale ProjectAtlas cache repair, MCP config generation, skill artifacts, host smoke tests, and fake-host tests for ProjectAtlas releases.
execute-spec-in-fork
Orchestrate one approved SPEC READY through a same-directory Codex App fork: create and name the execution task, ask it to run spec-executor, route decisions through Codex Task Messenger, validate the returned receipt, and archive a completed child. Use only when the user explicitly asks to execute an approved spec in…
breaking-down-the-work
Splits scope into a product-first work breakdown that follows the 100% rule, keeps pieces from overlapping, uses outline numbers, and gives every piece a dictionary entry. Use when an epic, feature, or new subsystem needs a clean split into deliverables, or one source of truth before folders or work begin. Do not use…
closing-stale-packets
Brings an abandoned or half-filled change packet to an honest terminal state by completing it, closing it with a recorded rationale, or deleting it. Use when ng status flags a scaffold or invalid packet, a long session left a draft behind, or work was abandoned mid-packet. Do not use for an actively in-progress…
staying-on-mission
Tests the current work against a written, lasting mission anchor and forces one choice, re-anchor, escalate, or stop. Use when an agent keeps finishing tasks but the work drifts from the goal, scope creeps, the same action repeats in a loop, or standards slip one small step at a time. Do not use for a tiny edit with…