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.
git 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/commands/banibratachatterjee/awesomesalesforceskills/consolidate-triggers)<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.
<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>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.00000 | $0.00399 |
| Opus 5 | $0.00000 | $0.00199 |
| Sonnet 5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
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 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.
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:
- Discover triggers (local grep + optional
validate_against_org) - Classify each trigger
- Draft the consolidation (new handler class + replacement trigger file)
- Metadata scaffolding (
Trigger_Setting__mdtrecord) - 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-flowfor the sObject to check for coexisting record-triggered flows/refactor-apexon 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.
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 · 64 lines · 0 tokens per session scan A 18ac5b1e2809
consolidate-triggers is a command published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (3 stars, last pushed 4mo 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.