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 mattmre/EVOKORE-MCP-PUBLIC --skill lead-research-assistantgit clone --depth 1 https://github.com/mattmre/EVOKORE-MCP-PUBLICWrote 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/mattmre/evokore-mcp-public/lead-research-assistant)<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/lead-research-assistant"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/lead-research-assistant/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/mattmre/evokore-mcp-public/lead-research-assistant"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/lead-research-assistant.svg" alt="Reviewed on agentmods" width="80" 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.00043 | $0.01439 |
| Opus 5 | $0.00022 | $0.00720 |
| Sonnet 5 | $0.00009 | $0.00288 |
| Haiku 4.5 | $0.00004 | $0.00144 |
Grade A, and why
lead-research-assistant 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 7d 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.
This is a copy
100% identical to lead-research-assistant — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lead Research Assistant
This skill helps you identify and qualify potential leads for your business by analyzing your product/service, understanding your ideal customer profile, and providing actionable outreach strategies.
When to Use This Skill
- Finding potential customers or clients for your product/service
- Building a list of companies to reach out to for partnerships
- Identifying target accounts for sales outreach
- Researching companies that match your ideal customer profile
- Preparing for business development activities
What This Skill Does
- Understands Your Business: Analyzes your product/service, value proposition, and target market
- Identifies Target Companies: Finds companies that match your ideal customer profile based on:
- Industry and sector
- Company size and location
- Technology stack and tools they use
- Growth stage and funding
- Pain points your product solves
- Prioritizes Leads: Ranks companies based on fit score and relevance
- Provides Contact Strategies: Suggests how to approach each lead with personalized messaging
- Enriches Data: Gathers relevant information about decision-makers and company context
How to Use
Basic Usage
Simply describe your product/service and what you're looking for:
I'm building [product description]. Find me 10 companies in [location/industry]
that would be good leads for this.
With Your Codebase
For even better results, run this from your product's source code directory:
Look at what I'm building in this repository and identify the top 10 companies
in [location/industry] that would benefit from this product.
Advanced Usage
For more targeted research:
My product: [description]
Ideal customer profile:
- Industry: [industry]
- Company size: [size range]
- Location: [location]
- Current pain points: [pain points]
- Technologies they use: [tech stack]
Find me 20 qualified leads with contact strategies for each.
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.
- 7d ago First seen · 203 lines · 43 tokens per session scan A 5f72662d5e5a
lead-research-assistant is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 3mo ago), licensed MIT. It adds 43 tokens to every session and 1,439 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to lead-research-assistant, differing in 5 lines, and is treated as a copy.
Other skills, from other repositories
law-of-similarity
Apply the Law of Similarity — shared colour, shape, or size signals that elements belong to one category. Use when signalling relationships across distance. For grouping by position, use law-of-proximity.
law-of-common-region
Apply the Law of Common Region — a shared container, background, or border groups elements regardless of spacing. Use when grouping must survive a tight layout. For grouping by spacing alone, use law-of-proximity.
version-control-strategy
Define version control for design files, components, and libraries — branching, naming, and release. Use when file history is chaotic. For design system contribution rules, use design-system-governance (design-systems).
presentation-deck
Structure a design presentation for a specific audience and decision. Use when presenting internally. For a portfolio narrative use case-study; for the written argument use design-rationale.
accessibility-test-plan
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use accessibility-audit (design-systems).
diary-study-plan
Design a diary study — prompts, cadence, duration, participant criteria, and analysis frame. Use when behaviour unfolds over days or weeks. For a single-session study, use usability-test-plan.