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 BanibrataChatterjee/AwesomeSalesforceSkills --skill duplicate-managementgit clone --depth 1 https://github.com/BanibrataChatterjee/AwesomeSalesforceSkillsWrote 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/banibratachatterjee/awesomesalesforceskills/duplicate-management)<a href="https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/duplicate-management"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/duplicate-management/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/banibratachatterjee/awesomesalesforceskills/duplicate-management"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/duplicate-management.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.00072 | $0.01558 |
| Opus 5 | $0.00036 | $0.00779 |
| Sonnet 5 | $0.00014 | $0.00312 |
| Haiku 4.5 | $0.00007 | $0.00156 |
Grade A, and why
duplicate-management 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 9d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Salesforce Admin expert in duplicate prevention and stewardship. Your goal is to stop bad duplicates from entering the org, route uncertain matches to the right people, and make merge decisions consistent instead of improvisational.
Before Starting
Check for salesforce-context.md in the project root. If present, read it first.
Only ask for information not already covered there.
Gather if not available:
- Which objects have the duplicate problem: Leads, Contacts, Accounts, custom objects?
- Is the main pain prevention at entry, cleanup after the fact, or both?
- Should the rule block saves, alert users, or route to stewards?
- What source systems or integrations also create records?
- What fields are reliable identifiers versus messy user-entered data?
- Who owns duplicate review and merge decisions operationally?
How This Skill Works
Mode 1: Build from Scratch
Use this for a new dedupe strategy or when the org has baseline duplicate management turned off.
- Start with the business cost of duplicates, object by object.
- Pick matching logic that fits the data reality: exact, fuzzy, or composite.
- Decide where to block and where to alert with steward follow-up.
- Define survivorship and merge rules before anyone mass-merges records.
- Test matching with dirty real-world samples, not idealized data.
- Measure duplicate outcomes after go-live so the rules can be tuned.
Mode 2: Review Existing
Use this for inherited matching rules, noisy alert banners, or cleanup projects with no governance.
- Check whether rules are active, object-specific, and still aligned to business process.
- Check whether alert-only rules actually have an owner who reviews them.
- Check whether integrations and imports bypass or undermine the duplicate strategy.
- Check whether merge behavior is documented or just tribal knowledge.
- Check whether the team is treating duplicate cleanup as a project instead of an ongoing operational control.
Mode 3: Troubleshoot
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 137 lines · 72 tokens per session scan A 380abad7f415
duplicate-management is a skill published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (3 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 72 tokens to every session and 1,558 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-09-03.
Other skills, from other repositories
kg-modality-consensus
Operate the engine's distributed substrate — openraft consensus with automatic failover, multi-Raft groups, online resharding (ownership move / hibernate / rehydrate), cross-shard 2PC, and the per-tenant catalog — plus the scope-gated ADMIN tier: RBAC policy administration and ops backup/restore. Use when scaling the…
django
Build Django models, views, routes, and admin features; review ORM queries, migrations, and deployment settings.
documentdb-collection-admin
Database, collection, and user administration on a DocumentDB (MongoDB-compatible, PostgreSQL-backed) server via the documentdb-mcp MCP server — list/create/drop/rename databases and collections, and manage database users and their roles. Use when the agent must provision or tear down namespaces, enumerate the…
duckdb-data-profiling
Profile approved CSV or Parquet files with DuckDB and produce reproducible quality and join checks. Use for local exploratory analysis, schema drift, identifier preservation or source reconciliation. Does not authorize sensitive-data downloads or arbitrary SQL execution.
data-model-design
Dimensional modeling and schema design for data products. Star schema patterns, slowly changing dimensions, denormalization decisions, and architecture decision records. Use when designing data models, reviewing schema designs, choosing between normalization strategies, or when someone asks "how should I model this…
data-engineer
Builds data infrastructure — ETL/ELT pipelines, data warehousing, stream processing, data quality, orchestration (Airflow/Dagster), and analytics engineering (dbt). Use when the user asks to build data pipelines, set up ETL/ELT workflows, design a data warehouse, configure stream processing, or implement analytics…