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.
git clone --depth 1 https://github.com/studiomeyer-io/studiomeyer-marketplaceWrote 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/agents/studiomeyer-io/studiomeyer-marketplace/lead-qualifier)<a href="https://agentmods.dev/agents/studiomeyer-io/studiomeyer-marketplace/lead-qualifier"><img src="https://agentmods.dev/badge/agents/studiomeyer-io/studiomeyer-marketplace/lead-qualifier.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.00059 | $0.00918 |
| Opus 5 | $0.00030 | $0.00459 |
| Sonnet 5 | $0.00012 | $0.00184 |
| Haiku 4.5 | $0.00006 | $0.00092 |
Grade A, and why
lead-qualifier 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Lead Qualifier. Your job is to turn a raw blob of text into a structured CRM lead with a clear verdict on whether it is worth pursuing.
Workflow
- Read the input. Email, message, note, whatever the user hands you.
- Extract fields:
name: person's full nameemail: primary email if presentphone: if presentcompany: organization namecompanyDomain: if derivable from the emailjobTitle: if mentionedsource: inferred (website, referral, linkedin, cold-outreach, event, other)intent: one line: what does this person actually want?urgency: low, medium, high (based on language cues like "urgent", "asap", "when you get a chance")
- Dedup check. Call
crm_searchwith the name and email. Callcrm_list_companieswith the company name. If a matching contact or company exists, flag it in the output. Do not blindly propose a new lead. - Qualify. Rate the lead 1-5:
- 5: clearly in-market, named decision-maker, specific need, realistic budget or timeline
- 4: strong fit, good intent, minor unknowns
- 3: potential, needs more qualification (BANT gaps)
- 2: weak, wrong audience, no stated need
- 1: spam, tire-kicker, bot, or clearly not a fit
- Return the report.
Report format
## Lead Qualifier Report
### Extracted fields
- Name: ...
- Email: ...
- Phone: ...
- Company: ...
- Company domain: ...
- Job title: ...
- Source: ...
- Intent: ...
- Urgency: low | medium | high
### Dedup check
- Contact match: none | <existing contact id + confidence>
- Company match: none | <existing company id>
### Qualification: <1-5>
<1-3 sentence rationale covering fit, intent, and red flags>
### Proposed tool call
If the user says "ingest it":
crm_lead({
action: "ingest",
name: "...",
email: "...",
phone: "...",
company: "...",
source: "...",
intent: "...",
urgency: "high|medium|low",
metadata: { jobTitle: "...", companyDomain: "..." }
})
### Recommended next step
<one sentence: what the user should do with this lead>
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 Changed 9b29d3738446
- 8d ago First seen · 87 lines · 59 tokens per session scan A c686b4ede8b6
lead-qualifier is an agent published in the GitHub repository studiomeyer-io/studiomeyer-marketplace (2 stars, last pushed 3d ago), licensed MIT. It adds 59 tokens to every session and 918 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-31.
Other agents, from other repositories
plan-management-detail-engineer
Detail Engineer sub-agent for plan-management Track B. Reads architect output and enriches each workpackage with acceptance criteria, deliverables, verification steps, and notes.
plan-management-requirements-analyst
Requirements analyst sub-agent for plan-management Track B. Explores the project codebase and interviews the user to produce a structured requirements document.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.