A process for executing an approved project plan one milestone at a time, with checks between milestones.

Use it to resume a mission, verify the project setup, run milestone work in order, and apply validation gates before continuing.

It keeps complex work organized and prevents later steps from starting while earlier work or its required checks are incomplete.

start — Skill for Claude Code by ohong/agent-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 ohong/agent-skills --skill start

Clone the repo

git clone --depth 1 https://github.com/ohong/agent-skills

Made for: Claude Code.

Or install mission, the plugin that ships this one along with the rest of its 6 skills.

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/ohong/agent-skills/start/github.svg)](https://agentmods.dev/skills/ohong/agent-skills/start)

Your own site

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

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

When invoked 980 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.00039	$0.00980
Opus 5.5	$0.00016	$0.00392
Sonnet 5.5	$0.00008	$0.00196
Haiku 4.5	$0.00004	$0.00098

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

Security

Grade A, and why

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

mission/skills/start/SKILL.md · 82 lines

How it starts

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

Mission Start — Enter the OODA Cycle

You are beginning execution. Each milestone is its own OODA cycle: orient to the milestone, act on it, observe the results, reorient for the next.

Pre-flight: Orient to the mission

Check that .mission/plan.md exists. If not: "No mission plan found. Run /mission:plan <task> first." Stop.
Check that .mission/progress.md exists. If not: "No progress file found. Run /mission:plan <task> first." Stop.
Read .mission/plan.md — load the full plan into your orientation.
Read .mission/progress.md — if milestones are already done, ask: "Previous progress detected. Resume with /mission:continue, or restart from milestone 1?"
Mismatch check: Read the plan's build/test/lint commands and run them once. Do they work? If not, fix the environment before starting. Starting with a broken environment means every observation will be contaminated.

Execution: The Milestone OODA Loop

Follow the execution protocol in ../../references/execution-protocol.md starting from Milestone 1.

Each milestone follows the OODA cycle:

Orient

Re-read .mission/plan.md for this milestone's goal and acceptance criteria
Re-read .mission/progress.md for current state
Read the source files you'll be modifying — never edit from memory
If .mission/learnings.md exists, check for relevant patterns

Decide (or act implicitly)

Familiar pattern? Act directly. Standard CRUD, common test setup, well-known library usage — move with implicit guidance.
Novel situation? Deliberate explicitly. Unfamiliar architecture, unexpected file structure, complex integration — slow down, read the relevant code, and think before acting.

Act

Write code, staying scoped to THIS milestone only
Commit after each meaningful change: mission(N/total): {description}
Every action is a hypothesis: "I believe this change will make the acceptance criteria pass"

Observe

Run ALL acceptance criteria. This is reality speaking to you — listen.
If they pass: update progress, proceed to next milestone
If they fail: you have a mismatch. Reorient before retrying. See failure recovery below.

Read the full file on GitHub · 82 lines

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 · 82 lines · 39 tokens per session scan A bcbb47c55e50

Subscribe to this mod's changes

start is a skill published in the GitHub repository ohong/agent-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 980 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-31.

Planning Project management

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.

Donchitos/Claude-Code-Game-Studios · 48 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

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…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens

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…

swan-gtm/gtm-skills · 160 tokens