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/analyze-field-impact)<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/analyze-field-impact"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/analyze-field-impact/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/analyze-field-impact"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/analyze-field-impact.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.00463 |
| Opus 5 | $0.00000 | $0.00231 |
| Sonnet 5 | $0.00000 | $0.00093 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
analyze-field-impact 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
/analyze-field-impact — Score the blast radius of renaming or deleting a field
Wraps agents/field-impact-analyzer/AGENT.md. Returns a risk-scored inventory of every place a field is referenced.
Step 1 — Collect inputs
Ask the user:
1. Object API name?
Example: Account
2. Field API name?
Example: Industry (or Industry__c for custom fields)
3. Target org alias (required — live-org probe is mandatory)?
Example: prod, uat, mydevsandbox
4. Intent: rename / delete / audit?
(Changes severity thresholds; default = audit)
5. Repo path (optional)?
Default: force-app/main/default
If target_org_alias is missing, STOP — the agent refuses without live-org access.
Step 2 — Load the agent
Read agents/field-impact-analyzer/AGENT.md in full, plus every file under Mandatory Reads Before Starting.
Step 3 — Execute the plan
Follow the 5-step plan exactly — confirm the field exists, enumerate repo references, enumerate org references via MCP tools (list_flows_on_object, list_validation_rules, tooling_query), score risk, propose mitigation.
Step 4 — Deliver the output
Return the Output Contract block:
- Summary with P0/P1/P2 + confidence
- Reference inventory table
- Risk breakdown
- Mitigation plan (phased, no auto-patch)
- Process Observations
- Citations
Step 5 — Recommend follow-ups
Based on what the agent found, suggest (but do not auto-invoke):
/design-objectif model-level redesign is implied/architect-permsif FLS cleanup is surfaced/preflight-loadif the field is in upcoming loads/detect-driftif the field appears in managed-package namespaces or unclear origins
What this command does NOT do
- Does not rename, delete, or modify the field.
- Does not analyze more than one field per invocation.
- Does not deploy any metadata patch.
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 · 71 lines · 0 tokens per session scan A d995e2871999
analyze-field-impact 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 463 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
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.