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/analyticsnpx skills add manusco/resonance --skill analyticsgit clone --depth 1 https://github.com/manusco/resonanceWhat 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.00062 | $0.01968 |
| Opus 5 | $0.00031 | $0.00984 |
| Sonnet 5 | $0.00012 | $0.00394 |
| Haiku 4.5 | $0.00006 | $0.00197 |
Grade A, and why
resonance-marketing-analytics 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 3d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/resonance-marketing-analytics: measure the question, not the tool
Expertise: turning marketing questions into instrumented events, defensible attribution, and experiments that do not lie. Apply when: someone needs a measurement plan, an event schema, an attribution decision, a north-star, or a verdict on whether a test actually moved the number.
You start from the decision, not the dashboard. A metric exists to change an action. If no decision hangs on a number, do not track it, and do not report it. Most analytics work fails not for lack of data but because the wrong question was instrumented, or none was.
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.
When a request spans owners, name the owner for each artifact and hand off with a brief. Do not collapse strategy, copy, asset production, and measurement into one skill just because the user named a channel.
What ships with it
9 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.
- evals/01_measurement_plan.json 1.3 KB
- evals/02_low_traffic_significance.json 1.3 KB
- evals/03_last_click_budget_cut.json 1.4 KB
- evals/04_planted_defect.json 1.3 KB
- evals/05_content_learning_loop.json 808 B
- references/attribution_models.md 9.1 KB
- references/content_learning_loop.md 1.4 KB
- references/experimentation_ops.md 9.3 KB
- references/measurement_plan.md 8.1 KB
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.
- 3d ago First seen · 80 lines · 62 tokens per session scan A 449dd33c2cdd
resonance-marketing-analytics is a skill published in the GitHub repository manusco/resonance (37 stars, last pushed 3d ago), licensed MIT. It adds 62 tokens to every session and 1,968 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
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…