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/instantkom/mcp-server/lead-qualifynpx skills add instantKOM/mcp-server --skill lead-qualifygit clone --depth 1 https://github.com/instantKOM/mcp-serverWrote 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/instantkom/mcp-server/lead-qualify)<a href="https://agentmods.dev/skills/instantkom/mcp-server/lead-qualify"><img src="https://agentmods.dev/badge/skills/instantkom/mcp-server/lead-qualify.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.00030 | $0.00876 |
| Opus 5 | $0.00015 | $0.00438 |
| Sonnet 5 | $0.00006 | $0.00175 |
| Haiku 4.5 | $0.00003 | $0.00088 |
Grade A, and why
lead-qualify 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Qualify and route an inbound lead
Runtime contract
- Delivery:
prompt - Minimum Agent Connect key scope:
draft - Minimum subscription tier:
business - Authentication: send the tenant-bound Agent Connect key as a Bearer token.
- Confirmation: Before invocation, obtain explicit user confirmation for the described mutation. A key scope grants technical permission; it is not user consent.
- Tenant, enabled-tool, PII-masking, rate-limit and audit gates are enforced by the MCP runtime. Never bypass or reproduce them client-side.
- Errors: stop on forbidden scope, invalid input, rate limiting or upstream failure; report the failure without inventing a successful result.
- Safe retry: keep the same inputs and idempotency key for a repeated mutation, inspect any prior result first, and never change inputs merely to bypass a conflict.
Workflow
Qualify and route an inbound lead
You are helping an instantKOM user triage fresh inbound conversations so real
sales opportunities are not lost in a noisy inbox. This is a draft playbook:
you may READ inbox data and PREPARE tags, notes and a reply draft, but you MUST
NOT send anything or auto-create records without explicit user confirmation.
Goal
For the given channelId, review conversations whose first inbound message is
within lookbackDays (default 7), score each against the rubric below, and hand
the user a ranked, actionable shortlist.
Qualification rubric (score each 0-3, judgement required)
Do NOT treat this as a keyword match -- read the actual message intent.
- Need / intent. Does the contact express a concrete problem, purchase intent, or question that maps to what the user sells? (0 = spam/off-topic, 3 = explicit buying intent.)
- Fit. Do signals (company mentioned, volume, use case, region/language) fit the user's target customer? Unknown fit scores 1, not 0.
- Timing / urgency. Is there a deadline, active evaluation, or "we need this now" signal?
- Reachability. Is the contact opted in and within a messaging window so a reply can actually be delivered?
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 First seen · 77 lines · 30 tokens per session scan A 26aed60a0044
lead-qualify is a skill published in the GitHub repository instantKOM/mcp-server (0 stars, last pushed 3d ago), licensed MIT. It adds 30 tokens to every session and 876 once invoked, about $0.0002 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 skills, from other repositories
LinkedIn automation via the Linked API CLI - fetch profiles, search people and companies, send messages, manage connections, create posts, react, comment, and run Sales Navigator and custom workflows. Use when the user wants to interact with LinkedIn.
nextjs-pages-router
Set up tRPC in Next.js Pages Router with createNextApiHandler, createTRPCNext, withTRPC HOC, SSR via ssr option and ssrPrepass, SSG via createServerSideHelpers with getStaticProps, and server-side helpers for getServerSideProps prefetching.
non-json-content-types
Handle FormData, file uploads, Blob, Uint8Array, and ReadableStream inputs in tRPC mutations. Use octetInputParser from @trpc/server/http for binary data. Route non-JSON requests with splitLink and isNonJsonSerializable() from @trpc/client. FormData and binary inputs only work with mutations (POST).
scalar-docs
Skill for writing and updating scalar.config.json — Scalar Docs configuration reference for users and LLMs.
horse-integration-tests
Guide for writing automated integration tests for Horse endpoints using DUnit/DUnitX and THTTPClient.
release-notes
Generate GitHub release notes for the Membrane api-gateway repo by collecting the commits between the last release and master, grouping them into Features / Improvements / Fixes / Security / Dependencies, and linking each to its PR. Use whenever the user wants to draft, extract, or write release notes / a changelog /…