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 beingsmit/technical-product-gtm --skill enterprise-onboardinggit clone --depth 1 https://github.com/beingsmit/technical-product-gtmWrote 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/beingsmit/technical-product-gtm/enterprise-onboarding)<a href="https://agentmods.dev/skills/beingsmit/technical-product-gtm/enterprise-onboarding"><img src="https://agentmods.dev/badge/skills/beingsmit/technical-product-gtm/enterprise-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/beingsmit/technical-product-gtm/enterprise-onboarding"><img src="https://agentmods.dev/badge/skills/beingsmit/technical-product-gtm/enterprise-onboarding.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00050 | $0.03317 |
| Opus 5 | $0.00025 | $0.01658 |
| Sonnet 5 | $0.00010 | $0.00663 |
| Haiku 4.5 | $0.00005 | $0.00332 |
Grade A, and why
enterprise-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.
This is a copy
98% identical to gtm-enterprise-onboarding — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 459 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enterprise Onboarding
Four-phase framework for onboarding enterprise customers from contract to value realization. The goal isn't just go-live — it's sustained adoption that doesn't cliff at Week 12.
When to Use
Triggers:
- "How do we onboard this enterprise customer?"
- "Customer went live but adoption is weak"
- "We keep losing customers 3 months after go-live"
- "POC to production transition"
- "How do I prevent Week 4 ghosting?"
- "Customer success onboarding framework"
Context:
- Enterprise or mid-market deals
- Complex technical requirements
- Multiple stakeholders involved
- 30-90 day implementation timelines
- Risk of churn during first year
Core Frameworks
1. The Week 4 Ghosting Problem (And How to Prevent It)
The Pattern:
Week 1: Kickoff call goes great. Everyone's excited. Week 2-3: Technical discovery, requirements gathering. Still good. Week 4: Customer stops responding. Meetings get cancelled. "Too busy."
What Happened?
You started customer onboarding before internal alignment on their side.
Who Owns This Project Internally?
- Sales rep? (Already moved to next deal)
- Technical champion? (Day job took over)
- Executive sponsor? (Delegates, doesn't drive)
- Nobody? (This is why they're ghosting)
The Framework: Internal Owner Validation
Before kickoff call, answer:
Who on customer side will:
- Attend weekly project meetings? (Not "invited" — will actually show up)
- Unblock issues with procurement/legal/security? (Has authority)
- Drive adoption with end users? (Has influence)
- Escalate when things stall? (Has executive access)
If you can't name a specific person for each, you don't have a project owner. You have a signed contract with nobody driving it.
How to Fix It:
During sales → CS handoff (before customer kickoff):
Sales rep must identify:
- Primary project owner (name, not role)
- Their capacity (dedicated or side project?)
- Their authority (can they unblock?)
- Their motivation (what's in it for them?)
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 · 459 lines · 50 tokens per session scan A 6141e52d0f87
enterprise-onboarding is a skill published in the GitHub repository beingsmit/technical-product-gtm (42 stars, last pushed 5mo ago), licensed MIT. It adds 50 tokens to every session and 3,317 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to gtm-enterprise-onboarding, differing in 5 lines, and is treated as a copy.
Other skills, from other repositories
customer-success-management
Runs the ongoing relationship with accounts after the sale — segmenting coverage against account value, building a health score that predicts rather than describes, running reviews customers find worth attending, forecasting renewals honestly, and finding expansion that follows usage instead of quota. Use this to…
chief-information-officer
The CIO's remit — running the technology the company works on, service quality, IT spend, and the boundary with product engineering. Use this to set IT priorities, decide what IT owns versus engineering, structure IT spend or an IT roadmap, judge whether to build, buy or outsource, or work out why IT is seen as a cost…
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
chief-operating-officer
Owns execution: how work actually gets done across the organization, including process, program management, capacity, vendors, supply chain, and service delivery. Use this when execution is the problem rather than strategy, to design or fix a process, to resolve cross-functional handoff failures, to plan capacity, to…
head-of-pmo
The EPMO lead's remit — what the PMO governs, what it must never become, and how it earns standing rather than compliance. Use this to stand up or reform a PMO, decide what it should and should not control, judge whether it is adding value or overhead, or work out why teams route around it.
chief-product-officer
Owns what gets built and why: product strategy, roadmap, discovery, user experience, and the definition of success for each release. Use this to decide what to build next, to cut scope, to turn a business goal into a product bet, to judge whether a feature is worth its cost, or when engineering and go-to-market…