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/tutorial/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/tutorial)<a href="https://agentmods.dev/skills/egregore-labs/egregore/tutorial"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/tutorial/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/tutorial"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/tutorial.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 Excessive Agency · line 247 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 430 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00061 | $0.00909 |
| Opus 5.5 | $0.00024 | $0.00364 |
| Sonnet 5.5 | $0.00012 | $0.00182 |
| Haiku 4.5 | $0.00006 | $0.00091 |
Grade B, and why
tutorial scanned grade B with 1 finding 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
Keep the experience conversational; never lecture or expose raw command output. How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tutorial
Guide the user through one real Local loop: orient → capture → connect → close. Keep the experience conversational; never lecture or expose raw command output.
When to invoke
Interactive walkthrough of Egregore's Local core loop — activity, reflection, and a quest — using adaptive questions and real Runtime-backed artifacts. Use for 'tutorial', 'walk me through Egregore', or 'show me how this works'; use onboarding for first-time identity or org setup.
Resume state
Read only tutorial and onboarding hints from .egregore-state.json. Reuse
onboarding.harvest_rounds to avoid repeated role/focus questions. reset
clears tutorial-only keys. Resume from the stored checkpoint; if already
complete, offer reset or normal work. Tutorial state is local product state,
not organizational memory or telemetry.
Reuse attached EGREGORE_ORG_CONTEXT_V1; do not repeat its retrieval or source
opens. The tutorial never calls QMD, graph, Git, control-plane storage,
publishing, sharing, notifications, or telemetry directly.
1. Orient
Ask only missing tailoring questions: work domain, then one domain-specific stage question. Fetch exactly one authorized activity snapshot and render it using the real activity surface:
bash bin/activity-data.sh 2>/dev/null \
| bash bin/node-run.sh bin/codex-skill-render.mjs activity-card -
Explain briefly that activity is the starting point for sessions, obligations, questions, and quests. Use “organizational memory,” never graph language.
2. Capture
Use the activity snapshot and onboarding focus to ask two adaptive questions:
- What throughline or hard problem matters now?
- What changed, remains blocked, or became clear?
The answer must concern the user's real work, not Egregore. Infer decision,
finding, or pattern (default finding), preview it, and explicitly confirm
the practice write. Render one complete body to a temporary file under tmp/, then call
exactly once; {artifact-file} is that file, and {artifact-type}, {title}, and
{topic} come from the confirmed insight:
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 · -538 lines · +16 tokens per session scan A → B e3d5c0211d36
- 1mo ago First seen · 640 lines · 45 tokens per session scan A 58b17bf68d64
tutorial is a skill published in the GitHub repository egregore-labs/egregore (293 stars, last pushed 9d ago), licensed MIT. It adds 61 tokens to every session and 909 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
gws-classroom
Google Classroom: Manage classes, rosters, and coursework.
get-rep-call-feedback
Use when the user wants evidence-backed coaching for one rep's calls, especially by comparing the rep with peer examples to identify repeatable best practices, specific upgrade moments, and practical next-call language.
tutorial
Interactive tutorial teaching Ouroboros hands-on.
recipe-create-classroom-course
Create a Google Classroom course and invite students.
printing-press-retro
Use when the user asks to retro, run a retrospective, file findings, or improve the Printing Press after a printed-CLI run. Trigger phrases: "retro", "retrospective", "what went wrong", "improve the press", "post-mortem", "lessons learned", "what can we improve", "file a retro", "submit findings". Do not use for…
socratic-quiz
Use this when the user wants to deeply understand something through guided questioning. Trigger phrases include: "quiz me", "help me understand", "Socratic", "teach me", "walk me through with questions", "test my understanding", or when the user asks for an explanation and would benefit more from guided discovery than…