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 matteotitta/genesys-skills --skill quickstart-onboardinggit clone --depth 1 https://github.com/matteotitta/genesys-skillsWrote 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/matteotitta/genesys-skills/quickstart-onboarding)<a href="https://agentmods.dev/skills/matteotitta/genesys-skills/quickstart-onboarding"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/quickstart-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/matteotitta/genesys-skills/quickstart-onboarding"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/quickstart-onboarding.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 122 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 122 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00164 | $0.02560 |
| Opus 5 | $0.00082 | $0.01280 |
| Sonnet 5 | $0.00033 | $0.00512 |
| Haiku 4.5 | $0.00016 | $0.00256 |
Grade A, and why
quickstart-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 12d 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/quickstart — onboard onto the marketing OS
Situation. Someone just got the link to the claude-code-marketing-quickstart repo — a fork-and-go marketing operating system built on the 4-systems framework (Context · Skills · Integrations · Orchestration), with a written 15-minute tour. Complication. A README is passive. People clone, skim, and stall before the first "aha" — the moment a real file lands in their spine from a skill they ran. That stall is where adoption dies. Question. How do we get a brand-new person from git clone to that first runnable win without them self-navigating a wall of text? Answer. This skill is the active wizard: it detects where they are, unblocks the exact next step, and drives them to run /competitor-research against a real target so they feel the framework in 15 minutes.
This onboards onto ONE canonical repo: matteotitta/claude-code-marketing-quickstart. The repo's README.md is the source of truth for the tour — this skill mirrors and drives it. The full beat-by-beat script + troubleshooting lives in the premium reference.
For an async handoff — distributing an MCP, plugin, or repo to a non-technical person you're not in a session with — use the one-paste install-prompt pattern in the premium reference. The pasted prompt carries the wizard when you can't.
Detect state → Exa key → Clone → Wire.env → Driven tour → THE AHA → Week-1 plan
↓ ↓ ↓ ↓ ↓ ↓ ↓
Phase 0 Phase 1 Phase 2 Phase 3 Phase 4 Phase 5 Phase 6
Modes
| Flag | Effect |
|---|---|
--mode beginner (default) |
"Knowledgeable friend" voice. Explain why each step matters; define jargon inline. Celebrate the wins (especially the Phase 5 file landing). |
--mode internal |
Operator-terse. Skip the encouragement; just sequence the steps + flag blockers. For you/team spinning up a fresh fork. |
Phase 0 — detect where they are (the dynamic part)
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.
- 12d ago First seen · 191 lines · 164 tokens per session scan A ac7ed6ac9827
quickstart-onboarding is a skill published in the GitHub repository matteotitta/genesys-skills (36 stars, last pushed 1mo ago), licensed MIT. It adds 164 tokens to every session and 2,560 once invoked, about $0.0008 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-30.
Other skills, from other repositories
gingiris-b2b-growth
🇺🇸 B2B SaaS Growth — PLG vs SLG Playbook — Diagnose whether your problem is distribution, pricing, or PMF. PLG/SLG selection by ACV and sales cycle, the 5-stage path from $0 to $10M ARR, NRR discipline, affiliate & channel motion, enterprise tiering. Built from HeyGen, Deel, Vercel, Supabase, Snowflake patterns.…
gr-b2b-growth
A guide to growing a business-to-business software product from early user research to large-scale sales. B2B software is sold to companies rather than individual consumers.
go-to-market-playbook
A reusable Go-to-Market strategy template for both B2B and B2C launches. Covers positioning, messaging, ICP definition, channel selection, and competitive analysis frameworks. By @WeiYipei.
leadmagic-cli
Use the LeadMagic CLI for enrichment automation — find emails, validate contacts, enrich CSVs in batch, find decision-makers by role, and push to outbound platforms (Smartlead, Instantly). Use when automating enrichment from the command line, batch-processing contacts, or integrating LeadMagic into scripts. Triggers…
revenue-team-onboarding
Revenue team onboarding — security access provisioning, ramp schedules, 30-60-90 plans, Slack engagement, shadowing, certification, and time-to-first-meeting reduction. Use when onboarding SDRs, AEs, managers, or RevOps hires. Triggers on: "sales onboarding", "SDR ramp", "30-60-90 sales", "reduce ramp time", "Slack…
team-management
Team management for startup leaders — 1:1s, performance reviews, goal setting (OKRs), delegation, feedback culture, remote team management, team rituals, and scaling from IC to manager. Use when building team processes, managing first direct reports, or scaling management as the company grows. Triggers on: "team…