start-task

start-task is a skill for Claude Code from Jamie-BitFlight/claude_skills. It costs 88 tokens per session (3,452 once invoked), scanned A, original, MIT.

A task-execution helper for SAM, a system that organizes development work into plans and tasks. It claims a task, loads its instructions, applies the acceptance criteria, and marks the task complete.

In plain words
What is it for?
It is for picking up a specific SAM task, implementing it, and completing it through the SAM tools.
Why use it?
It keeps task status and working context synchronized while an agent implements planned work. This avoids losing track of which task is active or whether it is finished.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: mentions subagents.

Part of the dh plugin — 70 skills, 29 agents shipped together

Good fit It is for picking up a specific SAM task, implementing it, and completing it through the SAM tools.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jamie-bitflight/claude_skills/start-task
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 Jamie-BitFlight/claude_skills --skill start-task
Clone the repo
git clone --depth 1 https://github.com/Jamie-BitFlight/claude_skills

Made for: Claude Code.

Or install dh, the plugin that ships this one along with the rest of its 70 skills, 29 agents.

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.

agentmods badge for start-task

README.md
[![agentmods](https://agentmods.dev/badge/skills/jamie-bitflight/claude_skills/start-task/github.svg)](https://agentmods.dev/skills/jamie-bitflight/claude_skills/start-task)
Your own site
<a href="https://agentmods.dev/skills/jamie-bitflight/claude_skills/start-task"><img src="https://agentmods.dev/badge/skills/jamie-bitflight/claude_skills/start-task/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.

agentmods 80×15 button for start-task

Your own site · 80×15
<a href="https://agentmods.dev/skills/jamie-bitflight/claude_skills/start-task"><img src="https://agentmods.dev/badge/skills/jamie-bitflight/claude_skills/start-task.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 88 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,452 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00088 $0.03452
Opus 5.5 $0.00035 $0.01381
Sonnet 5.5 $0.00018 $0.00690
Haiku 4.5 $0.00009 $0.00345

Measured 7d ago against content hash 708cfb2f3067, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

plugins/development-harness/skills/start-task/SKILL.md · 291 lines

How it starts

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

Start Task (SAM Task Execution Helper)

You are implementing a specific task in a SAM plan, addressed as P{id}/T{id}. The backend resolves that address and returns the task — no path is involved.

Use the SAM CLI's plan group for the runner sequence. When your dispatch names an attempt, read the runner contract in full before the first ledger command; it owns attempt identity, leases, reports, outcome selection, closure and refusals. Load dh:subagent-contract before returning your response; it owns the response destination and the distinction between recorded closure, durable outcome and immediate status.

<task_input> $ARGUMENTS </task_input>

Load dh:dh-cli-usage before using <sam_cli/> or <dh_scripts/> below.


Tool availability: task state moves through <sam_cli/>, which needs no MCP server. The artifact and backlog steps below use mcp__plugin_dh_backlog__* tools; if one is unavailable, load dh:dh-cli-usage and follow its MCP connection check.

Parse Arguments

  • plan_address (required): plan address in P{hex} form, e.g. Pdec8934d
  • --task <id> (optional): Task ID to start (defaults to first ready task)
  • --attempt <n> (optional): the attempt number the orchestrator opened for this dispatch. Carry it on every ledger command below. It is the key that proves a command belongs to this dispatch: a command from a superseded attempt is refused with stale-attempt.
  • --complete <id> (optional): Task ID to close

If --complete <task-id> Provided

With an attempt number, follow the runner contract's outcome selection, report prerequisites and closure steps for that attempt. --complete names the task to close; select its result from what happened rather than treating this argument as proof of success.

Without an attempt number, first read the task without --attempt and inspect its ledger attempts count. The direct route is available only when that count is zero. If any prior attempt exists, do not move it directly: return the applicable refusal or blocked response and route the task to that attempt's report-and-finish contract.

Read the full file on GitHub · 291 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.

  1. 7d ago Changed · +51 lines 708cfb2f3067
  2. 10d ago Changed · +19 lines · +13 tokens per session fe2ea6e87230
  3. 20d ago Changed · -69 lines 4f790099e26f
  4. 1mo ago Changed · +9 lines 3e4f2035aa3e
  5. 1mo ago Changed · +85 lines · +4 tokens per session 41a435082e70
  6. 1mo ago First seen · 196 lines · 71 tokens per session scan A a578c531121b

Subscribe to this mod's changes

start-task is a skill published in the GitHub repository Jamie-BitFlight/claude_skills (67 stars, last pushed 4d ago), licensed MIT. It adds 88 tokens to every session and 3,452 once invoked, about $0.0004 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-09-06.

Related

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.

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

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,"…

petrkindlmann/qa-skills · 124 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