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 manusco/resonance --skill market-researchgit 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/market-research)<a href="https://agentmods.dev/skills/manusco/resonance/market-research"><img src="https://agentmods.dev/badge/skills/manusco/resonance/market-research/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/manusco/resonance/market-research"><img src="https://agentmods.dev/badge/skills/manusco/resonance/market-research.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.00064 | $0.00730 |
| Opus 5 | $0.00032 | $0.00365 |
| Sonnet 5 | $0.00013 | $0.00146 |
| Haiku 4.5 | $0.00006 | $0.00073 |
Grade A, and why
resonance-research-market-research 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 10d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/resonance-research-market-research: discover Existential Data Points
Role: resonance-researcher Input: Target B2B SaaS category + Target company segment. Output: A structured EDP Market Research Report. Definition of Done: The output report contains verified category growth statistics, a competitive positioning grid, a catalog of 5-7 actionable Existential Data Points, and pain-based segmentation hypotheses. Free of AI slop and em dashes. Passed the validator.
Prerequisites (fail fast)
- SaaS Category (e.g., Sales Engagement Platforms) is identified.
- Target segment company size and industry is specified.
Algorithm
Copy this checklist and tick items as you go.
- Clarify Category: Confirm the specific SaaS vertical, company size, and target buyer profile before beginning. → verify: category boundaries are set.
- Examine Pain Points: Extract 3-5 acute, non-obvious operational frustrations that buyers in this vertical experience. → verify: each pain is backed by industry data or practitioner quote.
- Discover EDPs: Formulate 5-7 Existential Data Points (EDPs), the critical metrics or thresholds that create genuine buying urgency. → verify: each EDP is formatted with its specific metric, existential crisis logic, and an outreach hook.
- Segment Pains: Map these EDPs to 3 distinct pain-based target segments. → verify: each segment card has an outbound opening line hook.
- Source Verification: Group and cite all verified sources and market databases used during calculation. → verify: no statistics are fabricated.
Recovery
- Sizing data or market reports are unavailable or behind paywalls → utilize bottom-up estimation modeling (referencing tam-sam-som-methodology) to calculate proxy market values.
- Identified pains are too generic (e.g., "saves time") → halt analysis, perform deep practitioner review (e.g., searching forums or reviews), and rewrite with specific operational metrics.
- Tried to identify 5 EDPs but metrics feel weak → stop, pivot to evaluating the primary business risks of non-adoption (regulatory, cost-overhead, or competitor expansion), and 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.
- 10d ago First seen · 40 lines · 64 tokens per session scan A 839f23efc14d
resonance-research-market-research is a skill published in the GitHub repository manusco/resonance (37 stars, last pushed 6d ago), licensed MIT. It adds 64 tokens to every session and 730 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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…