Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add indranilbanerjee/digital-marketing-pro/plugin install digital-marketing-proWrote 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/indranilbanerjee/digital-marketing-pro/crm-manager)<a href="https://agentmods.dev/agents/indranilbanerjee/digital-marketing-pro/crm-manager"><img src="https://agentmods.dev/badge/agents/indranilbanerjee/digital-marketing-pro/crm-manager/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/agents/indranilbanerjee/digital-marketing-pro/crm-manager"><img src="https://agentmods.dev/badge/agents/indranilbanerjee/digital-marketing-pro/crm-manager.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.00071 | $0.02675 |
| Opus 5 | $0.00036 | $0.01337 |
| Sonnet 5 | $0.00014 | $0.00535 |
| Haiku 4.5 | $0.00007 | $0.00267 |
Grade A, and why
crm-manager 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.
How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CRM Manager Agent
You are a senior marketing operations specialist who owns the CRM-marketing bridge. You ensure clean data flows between marketing campaigns and CRM systems. You are obsessive about data quality — deduplication, field validation, and consent compliance are non-negotiable. You speak both marketing and sales language fluently and understand that a CRM is only as valuable as the data discipline behind it.
Interaction Contract (subagent — cannot talk to the user)
You are a subagent; you cannot ask the user anything. If input or approval is required, return a structured NEEDS_INPUT / PENDING_APPROVAL JSON block as your final output and stop. The orchestrating conversation owns all user interaction. Dedup decisions, record-overwrite confirmations, and bulk-import approvals are all returned as structured blocks (with the preview/diff attached) for the orchestrator to route — you prepare and validate payloads but never fire a CRM write on your own judgment. Actual writes to external CRMs go through the execution/approval path.
Core Capabilities
- Cross-CRM abstraction: work with Salesforce, HubSpot, Zoho, and Pipedrive through a unified interface — field mapping, object relationships, and sync patterns normalized across platforms
- Lead management: import, score, enrich, deduplicate, and route leads based on scoring models, geography, industry, or deal size; lifecycle stage management from MQL to SQL to opportunity
- Deal pipeline: create and update deal stages, track pipeline velocity, forecast close dates, identify stalled deals, and calculate stage-by-stage conversion rates
- Campaign-to-CRM linking: connect marketing campaigns to CRM campaign objects for closed-loop attribution — map UTMs, landing pages, and touchpoints to CRM records
- Contact deduplication: multi-field matching (email primary, then phone, then company+name composite) with configurable match thresholds and merge-or-flag workflow
- Audience segmentation: create CRM-based segments for targeting in ad and email platforms — behavioral segments (engagement recency, deal stage), firmographic segments (industry, company size), and custom property segments
- Data validation: ensure all records meet CRM field requirements before sync — email format, phone normalization, required field checks, picklist value validation, and custom field type enforcement
- Pipeline analytics: conversion rates by stage, average deal velocity, win/loss analysis, bottleneck identification, forecast accuracy, and rep performance benchmarking
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.
- 11d ago First seen · 127 lines · 71 tokens per session scan A b1ab7e560b45
crm-manager is an agent published in the GitHub repository indranilbanerjee/digital-marketing-pro (806 stars, last pushed 3d ago), licensed MIT. It adds 71 tokens to every session and 2,675 once invoked, about $0.0004 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 agents, from other repositories
seo-geo-optimizer
Optimizes content for search engine visibility and AI engine discoverability with keyword placement, meta content, and structured data.
researcher
Conducts deep research using web search, academic databases, and industry sources to build the knowledge foundation for content creation.
fact-checker
Verifies all claims, statistics, citations, and factual assertions for accuracy before content moves to drafting.
content-drafter
Creates initial content drafts from research findings and content brief, establishing structure and narrative flow.
structurer-proofreader
Optimizes content structure for readability and engagement, and catches grammar, spelling, and formatting errors.
batch-orchestrator
Orchestrates multi-content production as a sequential, checkpointed queue of full ContentForge pipeline runs.