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 packagegit 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/package)<a href="https://agentmods.dev/skills/myclaude-sh/myclaude-creator-engine/package"><img src="https://agentmods.dev/badge/skills/myclaude-sh/myclaude-creator-engine/package/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/package"><img src="https://agentmods.dev/badge/skills/myclaude-sh/myclaude-creator-engine/package.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.00052 | $0.05570 |
| Opus 5 | $0.00026 | $0.02785 |
| Sonnet 5 | $0.00010 | $0.01114 |
| Haiku 4.5 | $0.00005 | $0.00557 |
Grade A, and why
package 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 10d 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 — 456 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Packager
Stage a product for distribution with triple manifests (MyClaude + Anthropic Plugin + Agent Skills universal).
When to use: After /validate passes. Before /publish.
When NOT to use: If the product hasn't been validated yet (run /validate first).
Activation Protocol
- Shared preamble: Load
references/quality/activation-preamble.md— context assembly, persona adaptation, deterministic routing rules. - Identify product:
$ARGUMENTSas slug →workspace/{slug}/1b. Mode selection (Express vs Guided). Readcreator.yaml → preferences.workflow_style. Resolve the flow mode:--expressflag ORworkflow_style == "autonomous"→ Express mode. Skip the "confirm before stage" prompt, skip the manifest preview step, and produce a single post-stage summary. The safety invariants below still hold — only the conversational confirmations are trimmed.workflow_style == "guided"or missing → Guided mode (default). Confirm before staging, show manifest preview, and walk the creator through the pipeline with full voice.
- Read
.meta.yaml→ verify state is "validated" and MCS score >= 75% - Read
creator.yaml→ load author metadata for manifests. If missing → "Creator profile not found. Run/onboardfirst." and stop. - Maintain creator persona: Adapt language, depth, and examples to
profile.typeandtechnical_levelthroughout this skill's execution. A developer gets code examples; a domain expert gets plain language. - Load
product-dna/{type}.yaml→ get install_target - Load
config.yaml→ vault_defaults for missing fields 6b. Load proactives: Loadreferences/engine-proactive.md— wire #1 (pipeline guidance: after package, guide to /publish), #20 (test mandate: if MCS-2+ and.meta.yaml.test_result != "pass", block packaging with message "Run /test first"). - Load voice identity: Load
references/quality/engine-voice-core.md. Every user-facing line in this skill honors the ✦ signature, three tones, and six anti-patterns. - CLI contract: Load
references/cli-contract.mdfor unified error handling. This skill has conditional severity based on pricing model. Severity map:- Blocking (paid products only):
stripe status— if product price > 0 and Stripe not connected, halt packaging - Silent-skip (free products):
stripe status— irrelevant for free products, skip without warning - Silent-skip:
search --category {type} --sort price-desc— competitive pricing scan, skip without warning on failure - All queries: append
2>/dev/null, 15s timeout, treat invalid JSON as CLI absent
- Blocking (paid products only):
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.
- 10d ago First seen · 456 lines · 52 tokens per session scan A 8aa28c7d0aa6
package is a skill published in the GitHub repository myclaude-sh/myclaude-creator-engine (25 stars, last pushed 5mo ago), licensed MIT. It adds 52 tokens to every session and 5,570 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.
animation-patterns
SwiftUI animation patterns including springs, transitions, PhaseAnimator, KeyframeAnimator, SF Symbol effects, scroll-driven effects, mesh gradients, text renderers, and shader effects. Use when implementing, reviewing, or fixing animation or visual-effect code on iOS/macOS.