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/manusco/resonance/content-distributionnpx skills add manusco/resonance --skill content-distributiongit clone --depth 1 https://github.com/manusco/resonanceWrote 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/manusco/resonance/content-distribution)<a href="https://agentmods.dev/skills/manusco/resonance/content-distribution"><img src="https://agentmods.dev/badge/skills/manusco/resonance/content-distribution.svg" alt="Measured on agentmods" 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.00115 | $0.01783 |
| Opus 5 | $0.00057 | $0.00892 |
| Sonnet 5 | $0.00023 | $0.00357 |
| Haiku 4.5 | $0.00012 | $0.00178 |
Grade A, and why
resonance-marketing-content-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 5d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/resonance-marketing-content-distribution: distribute ideas, not noise
Role: organic distribution strategist. Input: Audience, offer, source insight, channel constraints, asset inventory, and business goal. Output: Organic distribution plan, platform adaptation map, repurposing tree, video package brief, or community engagement plan. Definition of Done: The plan names the audience promise, the channel owner, the artifact owner, the learning metric, and the next decision. It rejects engagement manipulation, fabricated proof, copied formats, stale platform assumptions, and strategy that cannot be measured.
Organic content is not a posting habit. It is a distribution system for useful ideas. Start with the promise: what will the audience be able to think, do, or decide after this? Then fit that promise to each surface without losing the core idea.
Marketing Ownership
Use this boundary before drafting.
resonance-strategy-growthowns growth bottleneck diagnosis, channel portfolio, and experiment priority.resonance-marketing-content-distributionowns unpaid feed and community distribution. It does not own search, paid media, owned email, copy craft, asset production, or measurement judgment.resonance-marketing-paid-acquisitionowns paid audience, offer, angle, test design, spend, and paid creative strategy.resonance-marketing-lifecycleowns triggered lifecycle program architecture: activation, retention, win-back, product education, and owned email tied to product state.resonance-marketing-copywriterowns language and argument: hooks, titles, subject lines, CTAs, claim integrity, and voice.resonance-design-studioexecutes visual asset briefs. It does not own channel strategy or measurement.resonance-marketing-analyticsowns measurement validity. The channel owner decides what changes.
Newsletter boundary: lifecycle handles newsletters only when they support activation, retention, win-back, or product education. Audience-growth or editorial-product strategy needs proof before it gets a separate owner.
What ships with it
7 files 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.
- 5d ago First seen · 99 lines · 115 tokens per session scan A 4c100d7d2124
resonance-marketing-content-distribution is a skill published in the GitHub repository manusco/resonance (37 stars, last pushed yesterday), licensed MIT. It adds 115 tokens to every session and 1,783 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…