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 agentmods add skills/ariadoss/superskills/creator-programnpx skills add ariadoss/superskills --skill creator-programgit clone --depth 1 https://github.com/ariadoss/superskillsWhat 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 | $0.00072 | $0.00949 |
| Opus 5 | $0.00036 | $0.00475 |
| Sonnet 5 | $0.00014 | $0.00190 |
| Haiku 4.5 | $0.00007 | $0.00095 |
Grade A, and why
creator-program 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 2d 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.
This is a copy
100% identical to creator-program — 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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Channels: Creator Program
Guides creator program strategy for AI/SaaS products. Long-term partnerships with creators for content co-creation and brand building. Differs from affiliate (sales focus) and influencer (paid promotion focus).
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product, audience, and content needs.
Identify:
- Product type: AI tool, design tool, CMS, marketplace
- Content need: Tutorials, templates, use cases
- Creator target: Followers, niche, content quality
Creator vs. Affiliate vs. Influencer
| Dimension | Creator Program | Affiliate | Influencer |
|---|---|---|---|
| Goal | Brand + content co-creation | Direct sales | Brand exposure |
| Incentive | Credits, free use, revenue share | Commission | Paid, product |
| Content | Must use product to create | Links | Influencer original |
| Relationship | Long-term | Transactional | Flexible |
Incentive Models
| Model | Use | Examples |
|---|---|---|
| Credits | AI tools; cost control | Credit-based AI tools |
| Payment | High-quality content; budget available | Paid creator programs |
| Hybrid | Credits + commission, brand partnership | Common for SaaS |
| Marketplace | Template/plugin sales; revenue share | Design tools, CMS marketplaces |
Implementation Phases
| Phase | Weeks | Tasks |
|---|---|---|
| Plan | 1–2 | Goals, incentives, application form, resources |
| Launch | 3–4 | Landing page, promotion, tracking |
| Recruit | 5–8 | Screen applications, outreach, onboarding |
| Co-create | 9–12 | Content publishing, support, promotion |
| Optimize | Ongoing | Metrics, feedback, incentive tweaks |
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.
- 2d ago First seen · 93 lines · 72 tokens per session scan A 063ff750d501
creator-program is a skill published in the GitHub repository ariadoss/superskills (9 stars, last pushed 18d ago), licensed MIT. It adds 72 tokens to every session and 949 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to creator-program, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…