lead-generation-crm

lead-generation-crm is a skill for Claude Code, Codex from m3taz-ahmed/ai-globals. It costs 36 tokens per session (647 once invoked), scanned A, original, MIT.

A process for collecting potential customers, adding useful company or person details, judging their fit and interest, and sending them through a customer-relationship management system, or CRM.

In plain words
What is it for?
Use it to capture leads from forms, messages, replies, webinars, or referrals; connect people to companies; score them; and route them to sales or follow-up campaigns.
Why use it?
It keeps leads in a trackable sales pipeline instead of scattered across spreadsheets or private messages, while supporting deduplication and follow-up routing.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to capture leads from forms, messages, replies, webinars, or referrals; connect people to companies; score them; and route them to sales or follow-up campaigns.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/m3taz-ahmed/ai-globals/lead-generation-crm
Install

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.

Any agent
npx skills add m3taz-ahmed/ai-globals --skill lead-generation-crm
Clone the repo
git clone --depth 1 https://github.com/m3taz-ahmed/ai-globals

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for lead-generation-crm

README.md
[![agentmods](https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/lead-generation-crm/github.svg)](https://agentmods.dev/skills/m3taz-ahmed/ai-globals/lead-generation-crm)
Your own site
<a href="https://agentmods.dev/skills/m3taz-ahmed/ai-globals/lead-generation-crm"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/lead-generation-crm/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.

agentmods 80×15 button for lead-generation-crm

Your own site · 80×15
<a href="https://agentmods.dev/skills/m3taz-ahmed/ai-globals/lead-generation-crm"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/lead-generation-crm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 647 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00036 $0.00647
Opus 5 $0.00018 $0.00324
Sonnet 5 $0.00007 $0.00129
Haiku 4.5 $0.00004 $0.00065

Measured 11d ago against content hash 676a308c3f83, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

lead-generation-crm 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 11d 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.

skills/lead-generation-crm/SKILL.md · 40 lines

What it actually says

[SKILL] lead-generation-crm [OBJ] Turn anonymous interest into qualified, tracked opportunities inside a CRM. Capture from every channel, enrich, score (fit/intent/behavior), and hand off to b2b-cold-outreach or client-onboarding.

[RULES]

  1. [REQ] Lead lifecycle: Capture → Enrich → Score → Nurture → Handoff. Each stage updates the CRM object; never keep leads in spreadsheets only.
  2. [CMD] Context7 IDs: twentyhq/twenty (metadata-driven CRM objects), hubspot/hubspot-crm (free tier API), chatwoot/chatwoot (omnichannel inbox, MIT).
  3. [REQ] Free-first CRM: Twenty (AGPL, self-host) default; HubSpot free tier as SaaS parity; Chatwoot for conversation capture. Salesforce/Pipedrive only as paid parity.
  4. [REQ] Data model (from Twenty): Company → Person → Opportunity → Activity. Map every inbound to a Person+Company; dedupe on email/domain.
  5. [REQ] Lead scoring: lead_scorer 0-100 from fit (ICP match), intent (page/deal signals), behavior (opens/clicks/visits). Route ≥70 to sales, 40-69 to nurture, <40 to cold list.
  6. [REQ] Capture points: website form, LinkedIn DM, cold reply, WhatsApp (see whatsapp-sms), webinar, referral. All must write to CRM, not DMs-only.
  7. [REQ] Enrichment free-first: Clearbit-free path = Apollo free tier / LinkedIn manual / web search. No PII scraping without consent; respect marketing-compliance.
  8. [REQ] Nurture handoff: low-score leads enter marketing-automation journey; high-score into b2b-cold-outreach sequence. Log every touch.
  9. [REQ] Arabic/RTL: Arabic company/person names stored with proper unicode; pipeline labels offered in ar/en; Chatwoot RTL inbox supported.
  10. [REQ] Pipeline hygiene: weekly review of stale (>14d no activity) opportunities; auto-reminder task created.

[PROHIBIT]

  1. No CRM write of leads lacking capture source + consent flag.
  2. No manual PII scraping violating platform ToS.
  3. No sales handoff without a score recorded.
  4. No storing credentials/API tokens in the CRM notes.
Changes

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.

  1. 11d ago First seen · 40 lines · 36 tokens per session scan A 676a308c3f83

Subscribe to this mod's changes

lead-generation-crm is a skill published in the GitHub repository m3taz-ahmed/ai-globals (5 stars, last pushed 3d ago), licensed MIT. It adds 36 tokens to every session and 647 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

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…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens