client-onboarding

client-onboarding is a skill for Claude Code, Codex from m3taz-ahmed/ai-globals. It costs 31 tokens per session (613 once invoked), scanned A, original, MIT.

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

In plain words
What is it for?
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.
Why use it?
It collects the information, signatures, payment, expectations, and access needed before delivery begins, reducing confusion and early project problems.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit 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.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/m3taz-ahmed/ai-globals/client-onboarding
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.

agentmods badge for client-onboarding

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.

agentmods 80×15 button for client-onboarding

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00031 $0.00613
Opus 5 $0.00015 $0.00307
Sonnet 5 $0.00006 $0.00123
Haiku 4.5 $0.00003 $0.00061

Measured 11d ago against content hash dda0c4972d9a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, 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 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.

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]

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

[PROHIBIT]

  1. No deliverable before contract signature.
  2. No kickoff without a written delivery plan.
  3. No PII in unsecured notes/commits.
  4. 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.

  1. 11d 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 2d ago), licensed MIT. It adds 31 tokens to every session and 613 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

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

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

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

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens