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.
npx agentmods add skills/breadchaincoop/labor.fun/sd-kickoffnpx skills add BreadchainCoop/labor.fun --skill sd-kickoffgit clone --depth 1 https://github.com/BreadchainCoop/labor.funWrote 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.
[](https://agentmods.dev/skills/breadchaincoop/labor.fun/sd-kickoff)<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>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.00064 | $0.00665 |
| Opus 5 | $0.00032 | $0.00332 |
| Sonnet 5 | $0.00013 | $0.00133 |
| Haiku 4.5 | $0.00006 | $0.00067 |
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.
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".
- Identify the quarter label from the assistant's ask message in this DM.
- Identify the member's KB slug: match the sender to a person file in
/workspace/shared-kb/people/(frontmatterdiscord_id/ platform ids). The slug is the filename without.md. - 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.
- path:
- 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.
- Read every file in
/workspace/shared-kb/sd/inputs/<QUARTER>/. - Use
/workspace/shared-kb/sd/template.mdas the skeleton when it exists; otherwise structure as: context → directives (3–6) → per-role hours → open questions. - Hours guidance: read
expected_hours_per_weekfrom/workspace/shared-kb/people/*.mdfrontmatter and recommend an hours range and a ceiling per role. Capacity is self-declared — label it as such; never present it as verified. - Note any committee members who filed no input, so the committee follows up.
- Save the draft to the KB (
sd/drafts/<QUARTER>.mdviamodify_kb_file), then post it — or a tight summary plus a pointer to the full draft — in the channel the task runs in.
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.
- 3d ago First seen · 54 lines · 64 tokens per session scan A cc13dd9a44f8
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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
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.
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.
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.
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…