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 myclaude-sh/myclaude-creator-engine --skill onboardgit clone --depth 1 https://github.com/myclaude-sh/myclaude-creator-engineWrote 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/myclaude-sh/myclaude-creator-engine/onboard)<a href="https://agentmods.dev/skills/myclaude-sh/myclaude-creator-engine/onboard"><img src="https://agentmods.dev/badge/skills/myclaude-sh/myclaude-creator-engine/onboard/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/myclaude-sh/myclaude-creator-engine/onboard"><img src="https://agentmods.dev/badge/skills/myclaude-sh/myclaude-creator-engine/onboard.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.00054 | $0.02360 |
| Opus 5 | $0.00027 | $0.01180 |
| Sonnet 5 | $0.00011 | $0.00472 |
| Haiku 4.5 | $0.00005 | $0.00236 |
Grade A, and why
onboard 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.
How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Onboarder
Discover and persist creator profile through intelligent scanning + minimal questions. Build creator.yaml — the Master Input that defines the quality ceiling for every product this creator builds.
When to use: First time using the Creator Engine, or when profile needs update (/onboard update).
Full protocol (phases, question scripts, schema, edge cases): Read ${CLAUDE_SKILL_DIR}/references/onboard-protocol.md before executing any phase.
Core Principle: Minimum Friction
RULE: Every question to the creator MUST use the AskUserQuestion tool. Never ask questions via plain text.
RULE: Scan first, ask second. Auto-detect everything possible. Only ask what cannot be inferred.
RULE: Optimize for the happy path. If the scan is rich enough, the entire onboarding should be 1 click.
Activation Protocol
- Shared preamble: Load
references/quality/activation-preamble.md— context assembly, persona adaptation, deterministic routing rules. - Check for
creator.yamlin project root - Exists → read
schema_version:schema_version < 3→ run Phase 2.5d Schema v2→v3 Silent Migration (protocol → Phase 2.5d) BEFORE any other action. Migration is atomic + reversible viacreator.yaml.bak.v2. After migration succeeds, continue with step 2 against the new v3 file.schema_version == 3→ load it, display summary, AskUserQuestion: "Is this still accurate?"- Yes → exit, profile is current
- No → enter UPDATE MODE (see protocol file → Update Mode Flow)
- Does not exist → enter FULL ONBOARDING (Phases 0 → 6c). Run Phase 2.5b (Intent Profile Inference) + 2.5c (Language Confirmation Gate) between Phase 2.5 and Phase 3 — both are mandatory for schema v3.
Full Onboarding — Phase Routing Table
Load ${CLAUDE_SKILL_DIR}/references/onboard-protocol.md for full details on every phase.
| Phase | What Happens | Detail Location |
|---|---|---|
| 0 — Platform Detection | Detect OS + shell + resolve {home} path |
protocol → Platform Detection |
| 1 — Silent Deep Scan | Run 5 scans in parallel: git identity, .claude/ root, project breadth, workspace, locale | protocol → Phase 1 |
| 2 — Inference Engine | Build draft profile: name, language, technical_level, profile.type, expertise. Weighted scoring (skills 3x, CLAUDE.md 3x, projects 2x, MCP 1x, rules 1x). Route to Express/Standard/Full path | protocol → Phase 2 |
| 2.5 — Disambiguation | If expert score (≥19) on Express/Standard path → one question: first time user? | protocol → Phase 2.5 |
| 2.5b — Intent Profile Inference | Derive 5 of 7 intent_profile fields from scan outputs (domain_depth, working_rhythm, maintenance_appetite, target_audience, external_dependency_tolerance). Mark _inferred: true. Defer licensing_tolerance to /create minds --genius. usage_frequency_expectation is asked in Phase 3 Call 2. Mandatory for schema v3. |
protocol → Phase 2.5b |
| 2.5c — Language Confirmation Gate | Classify language detection as high|low|fallback. Silent announcement if high; one-question confirm if low; forced question if fallback. Persist language_confidence + language_detection_sources. Mandatory for schema v3. |
protocol → Phase 2.5c |
| 2.5d — Schema v2→v3 Migration | Triggered only when an existing creator.yaml has schema_version < 3. Atomic + backed up to creator.yaml.bak.v2. Preserves all v2 fields. |
protocol → Phase 2.5d |
| 3 — Adaptive Questioning | Express (2 calls) / Standard (2 calls) / Full (3 calls). Call 2 of all three paths now includes a 4th question on usage_frequency_expectation (schema v3). |
protocol → Phase 3 |
| 4 — Profile Type | Infer type from all signals. Never ask directly | protocol → Phase 4 |
| 5 — Generate creator.yaml | Write schema v3 file (includes intent_profile, language_confidence, language_detection_sources). Validate YAML. Read back to verify. |
protocol → Phase 5 |
| 5b — Seed creator-memory.yaml | After creator.yaml is written and parses, seed the sibling creator-memory.yaml with a first_onboard event. Idempotent: silently skipped if a first_onboard event already exists. Validator: scripts/creator-memory-validate.py. Silent infrastructure — Phase 6 speaks, 5b prepares the ground. |
protocol → Phase 5b |
| 6 — Closing + Intelligence Report | Persona-adaptive next step + setup health + gap analysis + product recommendation. Load UX stack: references/quality/engine-voice-core.md (loaded at activation start), references/ux-experience-system.md (§2.3 first scaffold moment = "first onboard" for brand), references/quality/engine-voice.md (full Brand DNA substrate loaded here because this is a peak moment: the FIRST myClaude Studio impression). Use brand frame: ┌─ MyClaude Studio ─┐. Personalize with the name just captured. This is the moment the creator enters the myClaude universe — make it feel like arriving, not registering. After Phase 5 writes creator.yaml, Phase 5b appends the first_onboard event to creator-memory.yaml (create-if-absent with full schema shell per scripts/creator-memory-validate.py). This seeds the Ritual of Return Layer 2 for future sessions. |
protocol → Phase 6, 6b, 6c |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 131 lines · 54 tokens per session scan A 92329176162a
onboard is a skill published in the GitHub repository myclaude-sh/myclaude-creator-engine (25 stars, last pushed 5mo ago), licensed MIT. It adds 54 tokens to every session and 2,360 once invoked, about $0.0003 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
thinking-theory-of-constraints
When throughput or latency is pipeline-limited, identify the single binding constraint and exploit, subordinate, elevate, then recheck—ignore non-constraints.
Vizra ADK Memory System
Implement persistent memory, session context, and vector memory (RAG) for AI agents.
foundation-models
On-device LLM integration using Apple's Foundation Models framework. Use when implementing AI text generation, structured output, or tool calling.
analytics-interpretation
Interpret app metrics and make data-driven decisions. Covers DAU/MAU, retention, LTV, ARPU, App Store Connect analytics, AARRR funnel analysis, cohort analysis, and diagnostic decision trees. Use when user wants to understand their metrics, diagnose problems, or build a data-driven growth plan.
app-namer
Turn an app idea into validated, App-Store-ready name candidates. Use when the user says "name my app", "what should I call it", "app name ideas", "help me name this app", "is this name available", or needs to pick a brandable, ownable name before reserving it in App Store Connect.
in-app-events
Generates In-App Event metadata templates for App Store Connect — event names, descriptions, badge types, image specs, and deep link configuration. Use when creating events for App Store visibility, engagement campaigns, or seasonal promotions.