What is client-onboarding?

A repeatable process for starting work with a new client after a deal is signed.

Use it to run intake, prepare and sign a contract, issue the first invoice, make a delivery plan, hold kickoff, and provide a client portal or handbook.

It collects the information, signatures, payment, expectations, and access needed before delivery begins, reducing confusion and early project problems.

client-onboarding — Skill for Claude Code and Codex by m3taz-ahmed

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.

Any agent

npx skills add m3taz-ahmed/ai-globals --skill client-onboarding

Clone the repo

git clone --depth 1 https://github.com/m3taz-ahmed/ai-globals

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/client-onboarding/github.svg)](https://agentmods.dev/skills/m3taz-ahmed/ai-globals/client-onboarding)

Your own site

<a href="https://agentmods.dev/skills/m3taz-ahmed/ai-globals/client-onboarding"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/m3taz-ahmed/ai-globals/client-onboarding"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/client-onboarding.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 613 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00031	$0.00613
Opus 5.5	$0.00012	$0.00245
Sonnet 5.5	$0.00006	$0.00123
Haiku 4.5	$0.00003	$0.00061

Measured 1mo ago against content hash dda0c4972d9a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

skills/client-onboarding/SKILL.md · 38 lines

What it actually says

[SKILL] client-onboarding [OBJ] Turn a signed deal into a smooth, professional start. Run a repeatable intake→contract→invoice→kickoff flow that sets expectations and reduces early churn.

[RULES]

[REQ] Onboarding sequence (fixed order): (1) Intake form → (2) Contract via contract-studio → (3) First invoice via invoice-manager → (4) Delivery plan → (5) Kickoff call → (6) Client portal/handbook.
[REQ] Intake form fields: goals, scope, budget, timeline, stakeholders, communication channel, access needs. Store responses; never start work before intake complete.
[CMD] Context7 IDs: documenso/documenso (template→fields→sign→audit), invoiceninja/invoiceninja (client→invoice→payment), chatwoot/chatwoot (client inbox, MIT).
[REQ] Contract before work: always generate the engagement contract (NDA/SOW/MSA) via contract-studio and get signature before any deliverable. No signature = no start.
[REQ] First invoice: deposit/milestone-1 invoice issued on contract sign per invoice-manager. Net terms stated clearly (e.g., Net-7).
[REQ] Delivery plan: milestones, dates, review rounds, deliverables, acceptance criteria. Share in kickoff; align with dispute-resolution escalation path.
[REQ] Arabic/RTL: bilingual intake + contract + invoice when client is Arabic; RTL templates via arabic-freelance; currency in SAR/AED/EGP as appropriate.
[REQ] Portal/handbook: a single source of truth (Notion/Sheets/AIOS) with links, timeline, and contacts. Reduces "where is X" tickets.
[REQ] Kickoff agenda: recap goals, confirm scope, set cadence (weekly/ biweekly), define success metric, assign owners.
[REQ] Memory: record client profile, preferences, risks to aizee memory add for retention (client-retention).

[PROHIBIT]

No deliverable before contract signature.
No kickoff without a written delivery plan.
No PII in unsecured notes/commits.
No scope creep accepted during onboarding without change-order.

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.

1mo ago First seen · 38 lines · 31 tokens per session scan A dda0c4972d9a

Subscribe to this mod's changes

client-onboarding is a skill published in the GitHub repository m3taz-ahmed/ai-globals (5 stars, last pushed 5d ago), licensed MIT. It adds 31 tokens to every session and 613 once invoked, about $0.0001 per session on Opus 5.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.

Project management

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

qa-project-bootstrap

Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…

petrkindlmann/qa-skills · 124 tokens

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens