agentmods.dev

consolidate-triggers

consolidate-triggers is a command for Claude Code from BanibrataChatterjee/AwesomeSalesforceSkills. It costs 0 tokens per session (399 once invoked), scanned A, original, Apache-2.0.

A command that finds all Salesforce triggers on one object, such as Account or Opportunity, and creates a plan to combine them into one handler. Salesforce triggers are code that runs when records change.

In plain words
What is it for?
Use it to inspect local triggers, optionally compare them with a Salesforce org, draft a single-handler migration, and document deployment risks and sequencing.
Why use it?
Multiple triggers on the same object can make execution order and overlapping behavior difficult to manage. The command organizes discovery, classification, replacement code, metadata, and deactivation steps.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md).

not rated 4repo 6mo ago A scan 0 tokens original Apache-2.0

Good fit Use it to inspect local triggers, optionally compare them with a Salesforce org, draft a single-handler migration, and document deployment risks and sequencing.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/banibratachatterjee/awesomesalesforceskills/consolidate-triggers
View source ↗ BanibrataChatterjee/AwesomeSalesforceSkills
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.

Clone the repo
git clone --depth 1 https://github.com/BanibrataChatterjee/AwesomeSalesforceSkills

Made for: Claude Code.

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 consolidate-triggers

README.md
[![agentmods](https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/consolidate-triggers/github.svg)](https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/consolidate-triggers)
Your own site
<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/consolidate-triggers"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/consolidate-triggers/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 consolidate-triggers

Your own site · 80×15
<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/consolidate-triggers"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/consolidate-triggers.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 399 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.00000 $0.00399
Opus 5.5 $0.00000 $0.00160
Sonnet 5.5 $0.00000 $0.00080
Haiku 4.5 $0.00000 $0.00040

Measured 2mo ago against content hash 18ac5b1e2809, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

consolidate-triggers 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 2mo 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.

commands/consolidate-triggers.md · 64 lines

What it actually says

/consolidate-triggers — Consolidate N triggers on an sObject into one handler

Wraps agents/trigger-consolidator/AGENT.md. Finds every trigger on a given sObject and produces a single-handler migration plan using templates/apex/TriggerHandler.cls + TriggerControl.cls.

Step 1 — Collect inputs

Ask:

1. Which sObject should be consolidated?
   Example: Account, Opportunity, MyCustomObject__c

2. Path to your force-app tree?
   Default: force-app/main/default

3. Target-org alias (optional — enables an org-side trigger scan)

Step 2 — Load the agent

Read agents/trigger-consolidator/AGENT.md fully and every file under its Mandatory Reads Before Starting.

Step 3 — Execute

Follow the 5-step plan:

  1. Discover triggers (local grep + optional validate_against_org)
  2. Classify each trigger
  3. Draft the consolidation (new handler class + replacement trigger file)
  4. Metadata scaffolding (Trigger_Setting__mdt record)
  5. Deactivation plan (ordered deployment steps)

Step 4 — Deliver

Output per the agent's contract:

  • Discovery table
  • Proposed consolidation (full code blocks)
  • Migration step sequence
  • Risk notes (conflicting events, overlapping Flows)
  • Citations

Step 5 — Recommend follow-ups

After consolidation, recommend:

  • /analyze-flow for the sObject to check for coexisting record-triggered flows
  • /refactor-apex on the new handler to canonicalize its service/selector layers

What this command does NOT do

  • Does not refactor the business logic inside triggers — preserves verbatim.
  • Does not deploy anything.
  • Does not touch managed-package triggers.
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. 2mo ago First seen · 64 lines · 0 tokens per session scan A 18ac5b1e2809

Subscribe to this mod's changes

consolidate-triggers is a command published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (4 stars, last pushed 6mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 399 tokens. 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.

Planning
Related

consolidate-triggers compared with commands from other repositories

consolidate-triggers next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
consolidate-triggersBanibrataChatterjee/AwesomeSalesforceSkillsCommand46mo agoApache-2.0A0Claude Code
checklistgithub/spec-kitCommand148ktodayMITA13Claude Code
clarifygithub/spec-kitCommand148ktodayMITA27Claude Code
specifygithub/spec-kitCommand148ktodayMITA13Claude Code
analyzegithub/spec-kitCommand148ktodayMITA26Claude Code
convergegithub/spec-kitCommand148ktodayMITA35Claude Code
implementgithub/spec-kitCommand148ktodayMITA14Claude Code