sd-kickoff

sd-kickoff is a skill for Claude Code, Codex from BreadchainCoop/labor.fun. It costs 64 tokens per session (665 once invoked), scanned A, original, MIT.

A workflow for collecting quarterly Strategic Directives, meaning an organisation's priorities for the next quarter, from committee members and filing their responses in a shared knowledge base.

In plain words
What is it for?
Use it to identify the quarter and contributor, save their response under the matching knowledge-base path, and handle explicit declines.
Why use it?
It keeps submitted responses in the expected place and preserves each member's wording instead of leaving the organiser to file them manually.

Skill for Claude CodeCodex

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/breadchaincoop/labor.fun/sd-kickoff
Any agent
npx skills add BreadchainCoop/labor.fun --skill sd-kickoff
Clone the repo
git clone --depth 1 https://github.com/BreadchainCoop/labor.fun

Made for: Claude Code, 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.

agentmods badge for sd-kickoff

README.md
[![agentmods](https://agentmods.dev/badge/skills/breadchaincoop/labor.fun/sd-kickoff.svg)](https://agentmods.dev/skills/breadchaincoop/labor.fun/sd-kickoff)
Your own site
<a href="https://agentmods.dev/skills/breadchaincoop/labor.fun/sd-kickoff"><img src="https://agentmods.dev/badge/skills/breadchaincoop/labor.fun/sd-kickoff.svg" alt="Measured on agentmods" height="20"></a>
Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 665 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.

ModelPer sessionOnce invoked
Fable 5 $0.00064 $0.00665
Opus 5 $0.00032 $0.00332
Sonnet 5 $0.00013 $0.00133
Haiku 4.5 $0.00006 $0.00067

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

Security

Grade A, and why

sd-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 3d 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.

profiles/example/container-skills/sd-kickoff/SKILL.md · 54 lines

How it starts

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

Strategic Directives kickoff

The SD kickoff flow (a profile plugin) DMs each Strategic Directives committee member asking for next quarter's input, and keeps nudging until they respond. You are the receiving end: you file the inputs and, later, compose the first draft.

Filing a member's input (DM conversations)

Trigger: the conversation shows the assistant asked for "Strategic Directives input for " (e.g. 2026-Q3) and the user has now replied with their input — or says something like "file my SD input".

  1. Identify the quarter label from the assistant's ask message in this DM.
  2. Identify the member's KB slug: match the sender to a person file in /workspace/shared-kb/people/ (frontmatter discord_id / platform ids). The slug is the filename without .md.
  3. Save the input via modify_kb_file:
    • path: sd/inputs/<QUARTER>/<slug>.md
    • content: YAML frontmatter (author: <slug>, date: <ISO date>, quarter: <QUARTER>) followed by the member's input verbatim — do not summarize, do not edit their words.
  4. Confirm to the member: their input is filed and the nudges stop.

If they reply but explicitly decline to give input ("nothing from me this quarter"), file that too — a declared "no input" is a response; silence is what gets nudged.

Drafting the quarter's Strategic Directives (scheduled task)

Trigger: a scheduled task prompt referencing this skill's Drafting section.

  1. Read every file in /workspace/shared-kb/sd/inputs/<QUARTER>/.
  2. Use /workspace/shared-kb/sd/template.md as the skeleton when it exists; otherwise structure as: context → directives (3–6) → per-role hours → open questions.
  3. Hours guidance: read expected_hours_per_week from /workspace/shared-kb/people/*.md frontmatter and recommend an hours range and a ceiling per role. Capacity is self-declared — label it as such; never present it as verified.
  4. Note any committee members who filed no input, so the committee follows up.
  5. Save the draft to the KB (sd/drafts/<QUARTER>.md via modify_kb_file), then post it — or a tight summary plus a pointer to the full draft — in the channel the task runs in.

Read the full file on GitHub · 54 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. 3d ago First seen · 54 lines · 64 tokens per session scan A cc13dd9a44f8

Subscribe to this mod's changes

sd-kickoff is a skill published in the GitHub repository BreadchainCoop/labor.fun (2 stars, last pushed 2d ago), licensed MIT. It adds 64 tokens to every session and 665 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-31.

Related

Other skills, from other repositories

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

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

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 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