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 matteotitta/genesys-skills --skill client-onboardinggit clone --depth 1 https://github.com/matteotitta/genesys-skillsWrote 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/matteotitta/genesys-skills/client-onboarding)<a href="https://agentmods.dev/skills/matteotitta/genesys-skills/client-onboarding"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/client-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/matteotitta/genesys-skills/client-onboarding"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/client-onboarding.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00104 | $0.01714 |
| Opus 5 | $0.00052 | $0.00857 |
| Sonnet 5 | $0.00021 | $0.00343 |
| Haiku 4.5 | $0.00010 | $0.00171 |
Grade A, and why
client-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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Client onboarding
Generate comprehensive onboarding materials for new client engagements. Creates access checklists, asset gathering lists, and kick-off meeting agendas tailored to the project scope.
Doctrine inherited (Step 7 — 0626 rollout, locked 2026-06-04)
Output complies with output-tenets.md, output-simplicity.md, doc-output-structure.md. Step 6 calibration: see [[feedback_execution_doctrine_refinements_step6]].
Refinements applied: R1 (onboarding pack is client-team review surface — cites in appendix), R2 (multi-asset onboarding pack ships as one doc with toggles per asset: access checklist + assets list + kick-off agenda), R3 (welcome framing operator-direct, never "thrilled to have you"), R6 (close → kickoff scheduling primary), R9 (verb-led section names).
Process at a glance
INPUT VALIDATION → ACCESS CHECKLIST → ASSETS GATHER → KICK-OFF AGENDA → REVIEW & CHAIN
Five steps:
- Generate access checklist (tools by category, owners, access level)
- Create asset gathering list (per deliverable, with rationale)
- Design kick-off agenda (60-min, scope-specific context areas)
- Scaffold client folder (
projects/consulting/active/{client}/+ CLAUDE.md template) - Create brand hub if visual assets available (run
/brand-kitQuick mode), else schedule for Week 2
Full flowchart, step-by-step runbook, self-evaluation gate in the premium reference.
Claude Code triggers
Invoke this skill when user says:
- "Onboarding for [client]"
- "New client [name]"
- "Kick-off prep for [client]"
- "Starting with [client] tomorrow"
- "Onboarding checklist"
- "What do I need for the kick-off"
Do NOT invoke when:
- User wants discovery call prep → Use
client-discoveryskill - User wants to create a proposal → Use
client-proposalsskill - User wants to scaffold folder only → Use
new-clientskill
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 · 183 lines · 104 tokens per session scan A 1e2395e7e577
client-onboarding is a skill published in the GitHub repository matteotitta/genesys-skills (36 stars, last pushed 1mo ago), licensed MIT. It adds 104 tokens to every session and 1,714 once invoked, about $0.0005 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
recipe-create-doc-from-template
Copy a Google Docs template, fill in content, and share with collaborators.
sred-project-organizer
Take a list of projects and their related documentation, and organize them into the SRED format for submission.
notion
Notion CLI/API for pages, Markdown content, data sources, files, comments, search, Workers, and raw API calls.
slack-report-delivery
Deliver formatted network reports, audit results, topology diagrams, and compliance documentation to Slack channels with rich Block Kit formatting. Use when posting a health check report, sharing a security audit, delivering topology diagrams, or sending scheduled network reports to Slack.
notion
Search, read, create, and update Notion pages and databases. Supports knowledge capture, meeting prep, research documentation, and spec-to-task workflows.
google-workspace-ops
Operate across Google Drive, Docs, Sheets, and Slides as one workflow surface for plans, trackers, decks, and shared documents. Use when the user needs to find, summarize, edit, migrate, or clean up Google Workspace assets without dropping to raw tool calls.