Borrowing it
Nothing to install: this file belongs to egregore-labs/egregore. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/egregore-labs/egregore/main/.claude/skills/onboarding/SKILL.mdgit clone --depth 1 https://github.com/egregore-labs/egregoreWrote 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/egregore-labs/egregore/onboarding)<a href="https://agentmods.dev/skills/egregore-labs/egregore/onboarding"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/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/egregore-labs/egregore/onboarding"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/onboarding.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
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 →
- high Privilege Escalation · line 112 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 113 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00042 | $0.01390 |
| Opus 5.5 | $0.00017 | $0.00556 |
| Sonnet 5.5 | $0.00008 | $0.00278 |
| Haiku 4.5 | $0.00004 | $0.00139 |
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 24d 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Egregore onboarding
Welcome a new member through the deterministic VERIFY → ORIENT → INVITE → FIRST_HANDOFF flow. This is a conversation, not setup narration.
The Runtime adapter owns state migration, ActorContext authorization, Local/Connected detection, profile-witness verification, and identity reconciliation. AccountIdentity, ActorIdentity, and OrgMembership remain separate; GitHub fields are linked-provider aliases only. Never edit state or people files, call APIs/graph, or run Git from this skill.
When to invoke
Use for /onboarding, or when a new member's onboarding is incomplete — runs the resumable VERIFY, ORIENT, INVITE, FIRST_HANDOFF welcome flow through Egregore Runtime.
Start or resume
Run one bounded status command and suppress raw output:
mkdir -p tmp
bash bin/onboarding.sh status > tmp/onboarding-status.json
Read the fields for the flow below from the saved receipt:
jq -r '{phase, complete, usage_type, display_name, member_role, profile_fields_collected, installer_captured, invite_handled_by, profile_witness, ready, blockers} | to_entries[] | "\(.key): \(.value)"' tmp/onboarding-status.json
Use each printed field as its correspondingly named placeholder, such as
{phase}; quote placeholders in single quotes when you use them in a command,
and write any single quote inside a value as '\''.
The receipt reports the phase, completion state, user type, collected fields,
installer handoff, and canonical profile witness. It also migrates legacy
phase names safely. Do not inspect .egregore-state.json yourself.
- Complete with both
nameandrolecollected: say, "You're already set up. What are you working on?" and stop. - Complete with role missing: ask only their role, run
bash bin/onboarding.sh set-role "$ROLE", then ask what they are working on. - Installer-captured name: do not ask for it again.
- Invite handled by installer: do not offer another invite.
- Returning creator in
invite: explain that their previous work should be captured, then enter FIRST_HANDOFF.
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.
- 24d ago Changed · -276 lines · +4 tokens per session 3b72e03826a6
- 1mo ago First seen · 454 lines · 38 tokens per session scan A 2b26f0dbfa12
onboarding is a skill published in the GitHub repository egregore-labs/egregore (293 stars, last pushed 9d ago), licensed MIT. It adds 42 tokens to every session and 1,390 once invoked, about $0.0002 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
batch-api
Prepare a many-file, single-turn transform (translate, rewrite, extract) as a plan and submit it to the asynchronous, half-price DashScope Batch API; results are delivered as new files hours later. Invoke explicitly with /batch-api.
gws-calendar
Google Calendar: Manage calendars and events.
gws-gmail-send
Skill "gws-gmail-send" from googleworkspace/cli, covering gmail +send, usage, flags, examples and tips.
obsidian-bases
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.
gws-gmail-watch
Gmail: Watch for new emails and stream them as NDJSON.
gws-gmail
Gmail: Send, read, and manage email.