onboarding

onboarding is a skill for Cursor from gleanwork/cursor-plugins. It costs 92 tokens per session (1,692 once invoked), scanned A, a copy of onboarding, MIT.

A guided process for getting familiar with a new team, project, or work area. It collects the main responsibilities, important documents, current priorities, and people who can provide context.

In plain words
What is it for?
Use it to learn where a team or project is heading, what to read first, who owns relevant areas, and whom to talk to when joining unfamiliar work.
Why use it?
It gives a newcomer a focused starting point instead of requiring them to search through every document and conversation. It covers both the code and the human context around the work.

Skill for Cursor

Written for Cursor: shipped in a Cursor plugin.

Part of the glean plugin — 19 skills, 10 agents, 1 MCP server shipped together

Good fit Use it to learn where a team or project is heading, what to read first, who owns relevant areas, and whom to talk to when joining unfamiliar work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gleanwork/cursor-plugins/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 gleanwork/cursor-plugins --skill onboarding
Clone the repo
git clone --depth 1 https://github.com/gleanwork/cursor-plugins

Made for: Cursor.

Or install glean, the plugin that ships this one along with the rest of its 19 skills, 10 agents, 1 MCP server.

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 onboarding

README.md
[![agentmods](https://agentmods.dev/badge/skills/gleanwork/cursor-plugins/onboarding/github.svg)](https://agentmods.dev/skills/gleanwork/cursor-plugins/onboarding)
Your own site
<a href="https://agentmods.dev/skills/gleanwork/cursor-plugins/onboarding"><img src="https://agentmods.dev/badge/skills/gleanwork/cursor-plugins/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 onboarding

Your own site · 80×15
<a href="https://agentmods.dev/skills/gleanwork/cursor-plugins/onboarding"><img src="https://agentmods.dev/badge/skills/gleanwork/cursor-plugins/onboarding.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 92 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,692 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 100% copy Near-identical to another mod 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.00092 $0.01692
Opus 5.5 $0.00037 $0.00677
Sonnet 5.5 $0.00018 $0.00338
Haiku 4.5 $0.00009 $0.00169

Measured 1mo ago against content hash b2fe44f497b1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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.

Origin

This is a copy

100% identical to onboarding — 0 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.

glean/skills/onboarding/SKILL.md · 253 lines

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.

Team Onboarding

You are helping someone new get up to speed on a team or project. Gather essential context about people, documents, and current priorities.

Input

Determine the team or project from the user's request. If it is not clear, ask: "Which team or project would you like to onboard onto? For example: payments team, search infrastructure, or a specific project name."


Core Principles

  • Actionable over comprehensive: Focus on what to read and who to talk to
  • Technical and social: Include both code context and people context
  • Be skeptical: Not every doc found is essential reading
  • Quality over quantity: 5 must-read docs beats 20 "might be useful" links

Phase 1: Get Overview

Goal: Quick understanding of the team/project

Actions:

  1. Use Glean chat for a synthesized overview:
    chat "Give me an overview of the [team/project]. What do they own? What are their main responsibilities? What are they working on?"
    
  2. Summarize the overview for context

Phase 2: Find Key People

Goal: Identify who to meet and learn from

Actions:

  1. Find team members:

    employee_search "[team/project]"
    
  2. Build a people map:

    • Leadership: Who runs this team?
    • Senior folks: Who are the experienced people?
    • Recent hires: Who else is new?

Phase 3: Find Key Documents

Goal: Identify must-read docs and current priorities

Actions:

  1. Search for foundational docs:

    search "[team/project] onboarding OR getting started OR architecture"
    
  2. Search for recent activity:

    search query="[team/project]" updated="past_month"
    
  3. Find recent team meetings for current priorities:

    meeting_lookup "[team/project] past 2 weeks"
    

Phase 4: Vet All Content (CRITICAL)

Goal: Filter to truly essential items — BE SKEPTICAL

For each document, evaluate:

Essential Reading Test

  • Does someone new NEED to read this?
  • ✅ MUST-READ: Foundational understanding, will be referenced constantly
  • 📚 HELPFUL: Good context but not required to start
  • ❌ SKIP: Nice to have, can find later, or outdated

Read the full file on GitHub · 253 lines

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. 1mo ago First seen · 253 lines · 92 tokens per session scan A b2fe44f497b1

Subscribe to this mod's changes

onboarding is a skill published in the GitHub repository gleanwork/cursor-plugins (4 stars, last pushed 18d ago), licensed MIT. It adds 92 tokens to every session and 1,692 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to onboarding, differing in 0 lines, and is treated as a copy.