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 myths-labs/muse --skill growth-distributiongit clone --depth 1 https://github.com/myths-labs/museWrote 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/myths-labs/muse/growth-distribution)<a href="https://agentmods.dev/skills/myths-labs/muse/growth-distribution"><img src="https://agentmods.dev/badge/skills/myths-labs/muse/growth-distribution/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/myths-labs/muse/growth-distribution"><img src="https://agentmods.dev/badge/skills/myths-labs/muse/growth-distribution.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00125 | $0.05093 |
| Opus 5 | $0.00063 | $0.02547 |
| Sonnet 5 | $0.00025 | $0.01019 |
| Haiku 4.5 | $0.00013 | $0.00509 |
Grade A, and why
growth-distribution 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 — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Growth Distribution Skill
Multi-platform content distribution engine. Combines algorithm research with battle-tested DYA marketing execution.
⭐ 第零条铁律：先给价值，再带产品
This is the single most important rule. Everything else is secondary.
小红书规则核心逻辑："禁止低价值硬广，鼓励有价值分享"
| ✅ 正确顺序 | ❌ 错误顺序 |
|---|---|
| 先讲方法论/干货/真实经历 | 先推产品/功能介绍 |
| 再把 App 作为"实现方法的工具"自然带出 | 再讲"我们App能干嘛" |
| 算法判定：有价值内容 → 推流 | 算法判定：营销导流 → 限流 |
成功案例：solopro（438粉/1693赞藏）
- 498赞帖「如何搭建永不混乱的人生系统？」→ 先讲系统方法论，再展示App实现
- 344赞帖「在过一种一目了然的生活」→ 先讲生活理念，再自然引入工具
- 101赞帖「如何"真的"在24h内重启人生？」→ 疑问句标题+场景拆解+App是工具
DYA 适配示例
- ❌ 「同意吗APP上线了，功能介绍」
- ✅ 「恋爱中最该说清楚的3件事（第3件90%的人都忽略了）」→ 文末自然引出DYA
- ✅ 「一个人做了个App 被苹果拒3次终于上架了」→ 开发者故事（已验证有效：8赞8评251浏览）
- ✅ 「口头承诺为什么总是不靠谱？3个让约定真正生效的方法」→ 方法论+工具
Core Workflow
- Write content using value-first approach — Method/story first, product second
- Identify content type — Video (60s/15-30s/Reels) or text+image post
- Select platforms — Use platform priority matrix below
- Adapt content — Apply platform-specific rules from
references/platform-playbook.md - Visual consistency — Use unified brand style (see Visual Identity section)
- Schedule — Follow phased distribution timeline
- Post-publish — Execute first-hour engagement protocol
Platform Priority Matrix
| Priority | Platforms | Why |
|---|---|---|
| ⭐⭐⭐ | 小红书 · TikTok · 抖音 | Highest ROI for DYA's content type (争议性+情感+developer story) |
| ⭐⭐ | IG Reels · 微信视频号 | Original content boost + social chain amplification |
| ⭐ | B站 · X · Reddit · 微博 | Niche/long-tail/developer community |
Universal Rules (All Platforms)
- 先给价值再带产品 — The #0 rule above. Never lead with product.
- Front 3 seconds = life or death — Hook must grab within 3s or all platforms throttle
- No external links in post body — Bio + comment + self-reply only
- Comments >> Likes — Design content to spark discussion, not just appreciation
- Share/Repost = nuclear weapon — Content should trigger "tag your partner" impulse
- First hour is critical — Coordinate group members to engage within 60 min of posting
- 3 video versions: 60s full · 15-30s highlight · with/without URL watermark
- No cross-platform watermarks — IG penalizes TikTok watermarks and vice versa
- 不虚构互动数据 — 帖子不能写"收到私信""评论区炸了"等可被验证为假的描述
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 · 313 lines · 125 tokens per session scan A b564ec598710
growth-distribution is a skill published in the GitHub repository myths-labs/muse (32 stars, last pushed 4d ago), licensed MIT. It adds 125 tokens to every session and 5,093 once invoked, about $0.0006 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
context-receipts
Emit privacy-safe receipts for context selection, deferral, hydration, compaction, pruning, delegation, usage attribution, and boundary handoffs.
evidence-attestation
Emit privacy-safe evidence attestations for agent actions, reviews, memory answers, handoffs, scores, approvals, and tool dispatches.
skill-policy-receipts
Use when a task must obey a hard project policy, such as "do not generate tests for internal services", "do not call production APIs", or "do not edit generated files". Emits a privacy-safe receipt before writes and after guard checks.
requirements-authoring
To author, update, and validate functional/non-functional requirements as atomic units with user approval.
ijfw-workflow
Use when the user says: 'build', 'create', 'plan', 'new project', 'brainstorm', 'design', 'UI', 'website', 'dashboard', 'app', 'help me build', 'launch', 'book', 'campaign', or anything project-level. Skill body decides Quick vs Deep path.
ijfw-plan
Use when the user says 'plan this', 'plan it', 'make a plan', 'let's plan', 'draft a plan', 'how should we tackle this', 'break this down', or invokes '/ijfw-plan'. Produces a falsifiable PLAN.md (software, book, campaign, design, research) with task breakdown, dependency wave-table, and success criteria — gated by…