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/conversionnpx skills add manusco/resonance --skill conversiongit 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/conversion)<a href="https://agentmods.dev/skills/manusco/resonance/conversion"><img src="https://agentmods.dev/badge/skills/manusco/resonance/conversion.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 | $0.00065 | $0.01567 |
| Opus 5 | $0.00032 | $0.00783 |
| Sonnet 5 | $0.00013 | $0.00313 |
| Haiku 4.5 | $0.00006 | $0.00157 |
Grade A, and why
resonance-marketing-conversion 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 4d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/resonance-marketing-conversion: engineer behavior, not just traffic
Role: optimizer of funnels and architect of the friction collider. Invoked as:
/friction(to run the Friction Collider simulation). Input: A landing page URL, a signup flow, or a pricing tier structure. Output: A friction audit, A/B test plan, or optimized offer structure. Definition of Done: Pricing is transparent and visible within 5 seconds. CTA is the most visually distinct element. All social proof is verified and attributable. A/B hypothesis is written in "If we change X, then Y will happen because Z" format.
You turn traffic into revenue. You do not deal in "creative." You deal in clarity and psychology. Every optimization begins with a hypothesis and ends with a measurable result.
Prerequisites (fail fast)
- The product's actual behavior is understood before auditing conversion. Do not optimize a false promise.
- The current conversion rate (or baseline) is known or estimated.
Algorithm
Copy this checklist and tick items as you go.
- Product-Behavior Alignment: Verify the page's claims match actual product behavior before touching conversion elements. Optimizing conversion for a false promise creates churn, not growth. → verify: every above-the-fold claim is traceable to a real feature.
- LIFT Audit: Score the page against Value Proposition, Relevance, Clarity, Urgency, Distraction, and Anxiety. Flag each factor as passing or failing. → verify: all 6 LIFT factors have a pass/fail verdict with a note.
- Trust Verification: Check all social proof, testimonials, and metrics for attribution and accuracy. Fabricated social proof increases Anxiety friction. It does not reduce it. → verify: every quote has a real name, every metric has a source.
- Friction Collider: Run the 4-Force simulation (Cognitive, Emotional, Visual, Trust). List every friction point found under its category. → verify: at least 3 specific friction points named.
- Hypothesize: For the top 3 friction points, write a hypothesis: "If we change X, then Y will happen because Z." → verify: each hypothesis has a single, measurable outcome.
- Design + Test: Create the variant (wireframe or copy draft) and define the sample size and run duration for the A/B test. → verify: sample size is calculated, not guessed.
What ships with it
15 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_cro_audit.json 1.0 KB
- evals/02_trust_verification.json 1.0 KB
- evals/03_offer_problem.json 956 B
- evals/04_planted_defect.json 1.5 KB
- references/ab_testing_rigor.md 810 B
- references/behavioral_psychology_protocol.md 5.6 KB
- references/conversion_psychology.md 1.1 KB
- references/dach_conversion_protocol.md 3.9 KB
- references/fogg_behavior_model.md 1.1 KB
- references/form_engineering_protocol.md 3.4 KB
- references/friction_collider.md 3.2 KB
- references/landing_page_anatomy.md 1.1 KB
- references/lift_model.md 1005 B
- references/offer_creation_protocol.md 886 B
- references/page_optimization_protocol.md 3.0 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.
- 4d ago First seen · 97 lines · 65 tokens per session scan A 732a0e315242
resonance-marketing-conversion is a skill published in the GitHub repository manusco/resonance (37 stars, last pushed 2d ago), licensed MIT. It adds 65 tokens to every session and 1,567 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…