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 cwinvestments/memstack --skill client-onboardinggit clone --depth 1 https://github.com/cwinvestments/memstackWrote 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/cwinvestments/memstack/client-onboarding)<a href="https://agentmods.dev/skills/cwinvestments/memstack/client-onboarding"><img src="https://agentmods.dev/badge/skills/cwinvestments/memstack/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/cwinvestments/memstack/client-onboarding"><img src="https://agentmods.dev/badge/skills/cwinvestments/memstack/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.00065 | $0.02586 |
| Opus 5.5 | $0.00026 | $0.01034 |
| Sonnet 5.5 | $0.00013 | $0.00517 |
| Haiku 4.5 | $0.00006 | $0.00259 |
Grade A, and why
memstack-business-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 — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Client Onboarding: Setting up new client...
Produces a complete client onboarding package with welcome email, intake questionnaire, kickoff meeting agenda, access provisioning checklist, expectations document, and 30/60/90-day check-in schedule.
Activation
When this skill activates, output:
Client Onboarding: Setting up new client...
Then execute the protocol below.
Context Guard
| Context | Status |
|---|---|
| User says "client onboarding", "new client", "onboard client" | ACTIVE |
| User says "kickoff meeting", "intake form", "welcome email" | ACTIVE |
| User just signed a new client and needs to set up the engagement | ACTIVE |
| User wants a contract or agreement | DORMANT: use Contract Template |
| User wants to send an invoice | DORMANT: use Invoice Generator |
Common Mistakes
| Mistake | Why It's Wrong |
|---|---|
| "Start working immediately" | Without intake and alignment, you'll waste the first 2 weeks on rework. |
| "Skip the expectations document" | Unclear expectations cause 80% of client conflicts. Document everything upfront. |
| "No single point of contact" | Multiple client contacts = conflicting feedback. Designate one decision-maker. |
| "Forget access provisioning" | Waiting for logins and credentials delays the project by days or weeks. |
| "No check-in schedule" | Without scheduled touchpoints, small issues become big surprises. |
Protocol
Step 1: Gather Client Information
If the user hasn't provided details, ask:
- Client: company name, primary contact, industry
- Project: what was sold? (service type, scope, deliverables)
- Timeline: start date, key milestones, end date
- Communication: preferred channel (email, Slack, calls)?
- Access needed: what systems, accounts, or assets do you need from them?
Step 2: Send Welcome Email
Welcome email template:
Subject: Welcome aboard! Here's what happens next: [Your Company]
Hi [Client Name],
Welcome to [Your Company]! We're excited to work with you on [Project Name].
Here's what to expect in the next few days:
1. **Intake questionnaire** (attached / linked below), please complete
by [date, 2-3 business days]. This helps us understand your goals,
preferences, and current setup.
2. **Access provisioning**: we'll need a few logins and assets from you
(details in the questionnaire). The sooner we have access, the sooner
we can start.
3. **Kickoff call**: I've sent a calendar invite for [date/time].
This is a [30/60]-minute call where we align on goals, timeline, and
communication cadence.
Your primary point of contact is [Name] ([email]). For anything urgent,
you can also reach us at [phone/Slack].
If you have any questions before the kickoff, just reply to this email.
Looking forward to getting started!
[Your Name]
[Title]
[Company]
[Phone]
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 Changed 2582c65e96c2
- 1mo ago First seen · 301 lines · 65 tokens per session scan A ba95b8b19083
memstack-business-client-onboarding is a skill published in the GitHub repository cwinvestments/memstack (425 stars, last pushed 21d ago), licensed MIT. It adds 65 tokens to every session and 2,586 once invoked, about $0.0003 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
github-workflow
GitHub best practices for pull requests, code reviews, issues, Actions workflows, and repository management.
lerna
Best practices for Lerna monorepo management, versioning, and publishing.
nx
Best practices for Nx monorepo development, project configuration, and code generation.
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
customer-success
Support workflows, ticketing systems (Zendesk, Intercom), knowledge base design, chatbot design, and metrics (CSAT, NPS). Use when building support infrastructure, designing help centers, or optimizing customer experience.
event-planner
Event planning with timelines, budgets, vendor coordination, logistics checklists, and post-event evaluation. Use when organizing conferences, workshops, galas, or corporate events.