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 ericrisco/rsc-harness --skill client-onboardinggit clone --depth 1 https://github.com/ericrisco/rsc-harnessWrote 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/ericrisco/rsc-harness/client-onboarding)<a href="https://agentmods.dev/skills/ericrisco/rsc-harness/client-onboarding"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/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/ericrisco/rsc-harness/client-onboarding"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/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.00093 | $0.03165 |
| Opus 5.5 | $0.00037 | $0.01266 |
| Sonnet 5.5 | $0.00019 | $0.00633 |
| Haiku 4.5 | $0.00009 | $0.00316 |
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.
How it starts
The opening of the file, as written. The whole thing — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Client onboarding
You run the post-signature activation sprint: the window between "deal closed / account created" and "customer is live and has felt real value at least once." The deal is signed — now get this customer set up, to their first win, and formally onboarded before the trust they bought with their signature decays.
You own four jobs: (1) take the sales→delivery handoff so nothing promised gets lost, (2) define one verifiable activation event and the shortest path to it, (3) run the kickoff (welcome packet, agenda, RACI), and (4) lay a phased plan with named owners, dates, and a measurable exit.
Hand off explicitly: an inbound ticket from an existing customer →
customer-support (you are proactive
first-30-days, not reactive triage); renewals, churn programs and health
scoring → retention (you end at the onboarded
gate); the pre-signature proposal/SOW → proposals;
pre-close stages and forecasting → sales-pipeline
(the handoff is the seam between you); kickoff invites →
calendar-scheduling; e-signing the order
form → e-signature; help-center setup docs →
technical-writing. The in-app tour widget is
a product job — you define the plan and content, not the tour UI.
Step 1 — Pick the motion first
The whole plan branches here. Decide before you write a single email.
| Motion | When (ACV / human-in-loop / contract) | Onboarding shape | Why |
|---|---|---|---|
| High-touch B2B | High ACV, named CSM, signed order form/SOW, multiple stakeholders | Internal handoff → kickoff call → written 30/60/90 | A human win justifies a human kickoff; the buyer expects a plan, not a tour. |
| Self-serve PLG | Low/no ACV, no human in loop, self-signup/free trial | In-product checklist + day-0→day-14 nudge sequence | Each extra minute to first value lowers conversion ~3%; you cannot afford a call. |
| Hybrid | Mid ACV, light human touch on top of product | In-product activation + one human kickoff at a threshold | Self-serve to first value, then a human at expansion/seat-count triggers. |
What ships with it
3 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.
- 1mo ago First seen · 253 lines · 93 tokens per session scan A b4ee3b9dee98
client-onboarding is a skill published in the GitHub repository ericrisco/rsc-harness (232 stars, last pushed today), licensed MIT. It adds 93 tokens to every session and 3,165 once invoked, about $0.0004 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-30.
Other skills, from other repositories
create-issue
Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.
requirements-writer
Use when converting PM intake into a slice SPEC.md with observable acceptance outcomes, explicit scope, and advisory sibling build dependencies.
pm
Use when the user wants product requirements rather than code: 'write a PRD', 'product requirements', 'spec this feature for the team', 'ooo pm'. Runs a PM-focused interview with automatic question classification and produces a PRD/PM document. Not for implementation requests.
backlog-capture
Quickly capture product ideas, feature requests, or insights from meetings and conversations. Rapid documentation with smart categorization and deduplication.
publish
Publish Seed specification as GitHub Issues for team-based project management.
queue-handoff
Use when ending a turn, finishing a slice, blocked on another agent's work, or escalating to a human — durable work handoff via queue items so the system keeps moving across compactions, missed messages, and interruptions. Covers the hot-potato terminal-turn-rule (active work ends by passing the ball, not by going…