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 skills add KirKruglov/claude-skills-kit --skill project-onboardinggit clone --depth 1 https://github.com/KirKruglov/claude-skills-kitWrote 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/kirkruglov/claude-skills-kit/project-onboarding)<a href="https://agentmods.dev/skills/kirkruglov/claude-skills-kit/project-onboarding"><img src="https://agentmods.dev/badge/skills/kirkruglov/claude-skills-kit/project-onboarding/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.
<a href="https://agentmods.dev/skills/kirkruglov/claude-skills-kit/project-onboarding"><img src="https://agentmods.dev/badge/skills/kirkruglov/claude-skills-kit/project-onboarding.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00120 | $0.01436 |
| Opus 5 | $0.00060 | $0.00718 |
| Sonnet 5 | $0.00024 | $0.00287 |
| Haiku 4.5 | $0.00012 | $0.00144 |
Grade A, and why
project-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 11d 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: project-onboarding
Complete project onboarding for Claude Cowork in a single session.
Triggers
Russian: «создай проект», «onboarding проекта», «новый проект», «настрой проект», «создай контекст проекта», «быстрый контекст», «обнови карту файлов», «пересканируй файлы» English: "create project", "project onboarding", "new project", "set up project", "create project context", "quick context", "update file map", "rescan files"
Language Detection
Determine the language of the user's request:
- If the request is in Russian → use templates with
-rusuffix - Otherwise → use templates with
-ensuffix
All output (headings, labels, comments, instructions) must match the detected language.
Modes
| Mode | Triggers | Actions |
|---|---|---|
new |
"create project", "onboarding", "new project", "set up project" | Full interview → context.md + folder-instructions.md + file map + prompts |
quick |
"quick context", "create project context" | Blocks 1–3 + auto-scan → context.md |
scan |
"update file map", "rescan files" | File Map module only → update section in context.md |
Instructions
Step 1 — Determine Mode
If trigger matches scan → go directly to the File Map module.
If quick → interview blocks 1–3, then File Map.
Otherwise → new, all steps in sequence.
Step 2 — Interview (modes: new / quick)
Ask questions in blocks. Wait for a response after each block. Keep questions concise.
Block 1 — Basics
1. Project name?
2. Type: analytics / content / business / personal / other?
3. Status: Active / On hold / Completed?
4. Start date? Deadline?
Block 2 — Project Overview
5. Describe the project in 2–4 sentences.
6. Vision — what outcome = success?
Block 3 — Current Phase
7. What are we working on right now?
8. What is the concrete deliverable for this phase?
→ Mode quick stops here. Proceed to the File Map module.
Block 4 — Structure
9. Key elements / components / layers of the project?
What ships with it
8 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.
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.
- 11d ago First seen · 185 lines · 120 tokens per session scan A 61bb4663a531
project-onboarding is a skill published in the GitHub repository KirKruglov/claude-skills-kit (18 stars, last pushed 1mo ago), licensed MIT. It adds 120 tokens to every session and 1,436 once invoked, about $0.0006 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-30.
Other skills, from other repositories
github-issue-creator
Turn error logs, screenshots, voice notes, and rough bug reports into crisp, developer-ready GitHub issues with repro steps, impact, and evidence.
performance-review-assistant
TRIGGER THIS when conducting performance reviews, writing manager feedback, creating self-assessments, building peer feedback, developing PIPs, creating development plans, or handling difficult performance conversations. Helps write constructive, specific, actionable feedback that develops performance and documents…
onboarding-planner
TRIGGER THIS when preparing for new hires, planning first-day/week/month activities, creating onboarding schedules, building 30-60-90 day plans, designing welcome programs, organizing training schedules, or setting up buddy/mentorship programs. Designs comprehensive, engaging onboarding experiences that accelerate…
roadmap-builder
Build product roadmaps with quarterly planning, feature prioritization, dependency mapping, and stakeholder alignment. Create actionable roadmaps that communicate strategy and guide execution.
sprint-planning
Plan sprints with story point estimation, capacity planning, sprint goals, and retrospective frameworks. Organize teams for effective iteration with clear goals, realistic commitments, and continuous improvement.
onboarding-playbook
Design customer onboarding playbooks with milestone tracking, training plans, health checks, and success criteria.