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/cold-callnpx skills add manusco/resonance --skill cold-callgit 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/cold-call)<a href="https://agentmods.dev/skills/manusco/resonance/cold-call"><img src="https://agentmods.dev/badge/skills/manusco/resonance/cold-call.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.00062 | $0.00780 |
| Opus 5 | $0.00031 | $0.00390 |
| Sonnet 5 | $0.00012 | $0.00156 |
| Haiku 4.5 | $0.00006 | $0.00078 |
Grade A, and why
resonance-sales-cold-call 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/resonance-sales-cold-call: structure B2B cold call execution
Role: resonance-sales Input: Target description (seniority, role, company size, trigger event) + Sender's company offer. Output: A structured, speakable 6-part cold call script. Definition of Done: A speakable cold call script is generated containing Opener, Permission Framing, 3 Pain Hypotheses, Discovery, Mini Proof, and Meeting Ask. No AI slop or em dashes present. Passed the validator.
Prerequisites (fail fast)
- Target persona's seniority and industry is identified (price-seniority mapped).
- Product value proposition is climb-ladder mapped to an outcome (not just features).
Algorithm
Copy this checklist and tick items as you go.
- Opener: Draft a disarming, honest opener that states your name, company, and a pattern interrupt without asking "is this a good time?" or saying "how are you today?". → verify: hook is under 15 words.
- Permission Framing: Draft a permission request that gives the prospect explicit control and a clear exit to reduce immediate defensiveness. → verify: exit condition is stated clearly.
- 3 Pain Hypotheses: Formulate three specific pain hypotheses (functional, organizational, strategic) that lets the prospect self-diagnose their bottlenecks. → verify: each hypothesis is under 15 words.
- Discovery Questions: Design a single consequence-focused question that gets the prospect talking about the daily impact of their selected pain. → verify: only 1 main question is posed.
- Mini Proof: Formulate a brief, credible proof point ("companies like...") that establishes authority without generic or fabricated metrics. → verify: is under 3 sentences.
- Meeting Ask: Create a direct meeting ask offering a binary choice of two specific days and times for a brief 15-minute call. → verify: meeting length is capped at 15-20 minutes.
Recovery
- Prospect hangs up immediately → log as unreachable, do not re-dial same day.
- Prospect asks to "send an email" → redirect to value check: "happy to, but to keep it relevant, which of those three issues I mentioned is closest to what you're dealing with?"
- Tried to customize the script 3 times without a speakable flow → stop, run the 15-second read-aloud test, simplify vocabulary, escalate.
What ships with it
4 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 · 41 lines · 62 tokens per session scan A aa08ff3c4188
resonance-sales-cold-call is a skill published in the GitHub repository manusco/resonance (37 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 780 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.
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…