A starting workflow for taking a software ticket from a checked-out feature branch to an implementation-ready plan. It reads the repository's workflow rules and can route unclear or large tickets through extra planning steps.

Use it to fetch ticket details, explore the codebase, create or refine specifications and implementation plans, and prepare the work for implementation.

It provides context and structure before coding, so vague requirements and oversized tasks are identified early.

kickoff — Skill by sandsower

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.

agentmods

npx agentmods add skills/sandsower/beislid/kickoff

Any agent

npx skills add sandsower/beislid --skill kickoff

Clone the repo

git clone --depth 1 https://github.com/sandsower/beislid

Made for: Claude Code, Codex.

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

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

Security scan A 0 findings. Scan, not verified.

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	$0.00077	$0.01706
Opus 5	$0.00039	$0.00853
Sonnet 5	$0.00015	$0.00341
Haiku 4.5	$0.00008	$0.00171

Measured 2d ago against content hash 9e06f298f9e3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

kickoff 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 2d 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/kickoff/SKILL.md · 106 lines

How it starts

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

Start Work on Ticket

Turn a checked-out feature branch into an implementation plan. Kickoff is the front door: ticket → context → spec/blueprint/breakdown → update → implement Don't use this for: creating PRs, handling review/QA feedback, or PR handoff for completed work. Use ready-for-review or review-response for those.

Project config: <repo>/.beislid/workflow.md (see workflow-md-format.md). Probe lazily; policy-check side effects per action-policy-protocol.md. Output follows templates.

Read workflow.md

Read <repo>/.beislid/workflow.md. If missing, hard-fail and stop:

🛑 No workflow.md found in .beislid/. If this is a fresh project, run /setup to create one. If you moved your config, restore it to <repo>/.beislid/workflow.md.

Validate line 1 is exactly . If missing or wrong, hard-fail and stop; kickoff will not silently mis-parse.

When beislid:agent_isolation is present, load workspace placement plus the current host adapter before the first repo write. Run ensure_orchestrator_workspace; a requested transition requires a clean source and acknowledged destination, or kickoff stops with the configured manual fallback.

Compute cache identifiers:

repo_hash=$(git rev-list --max-parents=0 HEAD | sort | head -c 12)
workflow_hash=$(git hash-object .beislid/workflow.md)

Try to read ${BEISLID_STATE_DIR:-$HOME/.local/state/beislid}/probes/<repo_hash>.json:

Missing → empty in-memory probe state; cache state cold.
workflow_hash mismatch → empty in-memory probe state; cache state stale.
Hash matches → load capability entries; cache state fresh. Per-cap freshness uses probe_cache.ttl_hours, default 24.

Print orientation prose from kickoff-templates.md (≤240 chars).

On continue this ticket / continue from checkpoint, read .beislid/checkpoints/latest.json first. Prefer matching kickoff_context_ready; ask if unclear. Use as planning context; validate the live ticket first. Bad/missing pointers are non-blocking. beislid run-ledger resume --flow kickoff --ticket-id <id> --branch <branch> may add context but never replaces live validation or checkpoints.

Read the full file on GitHub · 106 lines

Files

What ships with it

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

2d ago First seen · 106 lines · 77 tokens per session scan A 9e06f298f9e3

Subscribe to this mod's changes

kickoff is a skill published in the GitHub repository sandsower/beislid (10 stars, last pushed 3d ago), licensed MIT. It adds 77 tokens to every session and 1,706 once invoked, about $0.0004 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-31.

Git and workflow Planning Productivity

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens