A planning guide that turns a confirmed feature description into an ordered implementation plan before coding begins. The plan names files, steps, checks, tradeoffs, and dependencies.

Use it to break a feature into coding tasks, choose between implementation approaches, identify files to change, and record unresolved blockers.

It reduces the risk of starting with an unclear approach or missing important work. Each step can be checked independently as the feature is built.

ss-plan — Skill for Codex by bonnguyenitc/specship

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 bonnguyenitc/specship --skill ss-plan

Clone the repo

git clone --depth 1 https://github.com/bonnguyenitc/specship

Made for: Codex.

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/bonnguyenitc/specship/ss-plan/github.svg)](https://agentmods.dev/skills/bonnguyenitc/specship/ss-plan)

Your own site

<a href="https://agentmods.dev/skills/bonnguyenitc/specship/ss-plan"><img src="https://agentmods.dev/badge/skills/bonnguyenitc/specship/ss-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/bonnguyenitc/specship/ss-plan"><img src="https://agentmods.dev/badge/skills/bonnguyenitc/specship/ss-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

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

Security scan A 1 finding. 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.00086	$0.02274
Opus 5.5	$0.00034	$0.00910
Sonnet 5.5	$0.00017	$0.00455
Haiku 4.5	$0.00009	$0.00227

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

Security

Grade A, and why

ss-plan scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- For each step define: **what changes**, **which files** (`path`), and a **verify** check. The `verify:` must be **executable, not a description** — a concrete command or test the coding loop can run and read a pass/fai

skills/ss-plan/SKILL.md · 94 lines

How it starts

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

Plan

Goal: turn an understood spec into a concrete, ordered implementation plan — small steps, each independently verifiable — before any code is written.

When to use

The spec is understood (ideally via the ss-spec skill) and you're ready to design.
You're asked to break a feature into steps or weigh implementation approaches.
Second stage of the workflow: spec → plan → coding → review (+ debug).

Shared task state

Part of the task pipeline — see ../WORKFLOW.md for the full contract.

Hydrate: resolve the active TASK-<ID>, read tasks/TASK-<ID>/task.md + spec.md, plus docs/onboarding/{source-structure,how-to-code}.md if present. If spec.md is missing or status: draft with open blockers, run ss-spec first.
Checkpoint: write plan.md, then update task.md — set stage: plan, plan artifact draft→approved, bump updated:, append a Pipeline Log line carrying your agent label (format: ../WORKFLOW.md → Agent handoff).
Blocked? If planning can't be finalized because of an unresolved blocker Q# or an external dependency (an API/data/decision the plan hinges on), set status: blocked, note it in Blocked by:, and log it; flip back to active when it clears. blocked is involuntary — to set the task aside by choice, use ss-pause-task. See ../WORKFLOW.md → Status values.
Lessons: read tasks/LESSONS.md at hydrate and apply its rules; if you detect a process mistake, fix it and append an L# entry there (see ../WORKFLOW.md → Lessons).

Method

1. Read the inputs

Read tasks/TASK-<ID>/spec.md (produced by ss-spec) — every step must trace to a requirement or acceptance criterion in it, and its Assumptions can decide the design, so read them too. If it's missing, run ss-spec first.
Know where the code will live and the patterns to follow: reuse docs/onboarding/source-structure.md and how-to-code.md if present, or run ss-explore-source if the project is unfamiliar.
Open the actual files the plan will touch — confirm the functions, signatures, and patterns the steps rely on really exist as you believe. A plan referencing imagined code doesn't fail now; it fails at coding, where it's more expensive.
Delegate wide reads to a subagent. If confirming the plan's assumptions requires broad exploration (an unfamiliar area, many candidate files), spawn the ss-explorer agent if your platform can spawn it (ships with specship for Claude Code), else the built-in Explore agent, for the fan-out and keep only its conclusions in this thread - but still open the specific files the steps touch yourself, and verify any path or symbol an agent reports before the plan relies on it. If your platform can't spawn subagents, do the exploration inline in this thread instead (../WORKFLOW.md → In-stage subagents: delegation is an optimization, never a precondition).

Read the full file on GitHub · 94 lines

Files

What ships with it

1 file 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.

agents/openai.yaml 301 B

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.

1mo ago First seen · 94 lines · 86 tokens per session scan A 1553bc969f17

Subscribe to this mod's changes

ss-plan is a skill published in the GitHub repository bonnguyenitc/specship (2 stars, last pushed 2mo ago), licensed MIT. It adds 86 tokens to every session and 2,274 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Planning agent agent-skills agent-workflow claudecode codex coding

html-artifacts

Author the HTML for a plan artifact, dashboard iframe, or Slack attachment — structure, design plan, available runtime, theming, and craft. Read this before writing HTML for publishartifact, outputiframe, or slackattachhtml.

langchain-ai/open-swe · 52 tokens

workspaces

How an Open SWE workspace's sandbox image works and how to change it — create one, edit or fork an existing one, start from scratch, what setupscript and updatescript are for, why a nightly refresh failed, where the build logs are, and how to read a rebuild in progress. Read this whenever someone asks about…

langchain-ai/open-swe · 89 tokens

baby-sit

Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.

langchain-ai/open-swe · 30 tokens

linear-tickets

Create or update high-quality Linear tickets while preserving the originating report, diagnostic links, attachments, and reporter/requester attribution. Read this whenever someone asks to create, recreate, or update a Linear issue.

langchain-ai/open-swe · 44 tokens

shap

Model interpretability and explainability using SHAP (SHapley Additive exPlanations). Use this skill when explaining machine learning model predictions, computing feature importance, generating SHAP plots (waterfall, beeswarm, bar, scatter, force, heatmap), debugging models, analyzing model bias or fairness, comparing…

synthetic-sciences/openscience · 109 tokens

rowan

Cloud-based quantum chemistry platform with Python API. Preferred for computational chemistry workflows including pKa prediction, geometry optimization, conformer searching, molecular property calculations, protein-ligand docking (AutoDock Vina), and AI protein cofolding (Chai-1, Boltz-1/2). Use when tasks involve…

synthetic-sciences/openscience · 115 tokens

ss-plan