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/onboardingnpx skills add BreadchainCoop/labor.fun --skill onboardinggit clone --depth 1 https://github.com/BreadchainCoop/labor.funWhat 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.00069 | $0.01387 |
| Opus 5 | $0.00034 | $0.00694 |
| Sonnet 5 | $0.00014 | $0.00277 |
| Haiku 4.5 | $0.00007 | $0.00139 |
Grade A, and why
onboarding 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.
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Onboarding
You're meeting this group for the first time. Get useful fast, don't interrogate. One short intro message, then a couple of batched questions, then go set things up. Total: a few messages, not a form.
When this runs
- Auto-detect: your group
CLAUDE.mdis still the stock template (only the{{ASSISTANT_NAME}}-substituted boilerplate, no org-specific notes added below it) and this is the first real message in the group. - On request: a user says "set yourself up", "onboarding", or similar, any time — treat it as a request to (re)run this even if memory already has content.
If memory already shows prior onboarding notes (see below) and nobody asked for it explicitly, don't re-run — you're done, just help them.
Step 1 — Introduce yourself (one message)
Short and concrete. Name (your configured assistant name), what you're for, one line on how to talk to you. Example shape:
Hi, I'm {{ASSISTANT_NAME}} 👋 I can answer questions, keep notes on your team, schedule reminders/summaries, and connect tools like GitHub. Give me a minute to get oriented — I'll ask a couple of quick questions.
Don't wait for a reply before moving to Step 2 — keep momentum.
Step 2 — Batch the basics (one message, not five)
Ask together, in one message, with sensible defaults so a one-line reply is enough:
- What should we call you / this assistant? (default: keep the current configured name — only rename if they want something different in this group's tone; a real org-wide rename is host-level, see below)
- Timezone — guess it if you can (from
people/entries already in the shared KB, or system locale) and ask them to confirm or correct rather than asking blind. - Response style — brief default options: concise/to-the-point vs. more conversational. Default to concise if they don't care.
- What does the team/org do? — one or two sentences is plenty.
- Who's here and what do they do? — names + rough roles for the people in the channel. Don't demand a full roster; take what's offered and move on.
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 · 130 lines · 69 tokens per session scan A be9127cf5f13
onboarding is a skill published in the GitHub repository BreadchainCoop/labor.fun (2 stars, last pushed 5d ago), licensed MIT. It adds 69 tokens to every session and 1,387 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…