agentmods.dev

sf-debug

sf-debug is a skill for Claude Code, Codex from divingsbysangam/salesforce-compound-engineering-plugin. It costs 95 tokens per session (889 once invoked), scanned A, original, MIT.

A structured debugging skill for Salesforce applications, including Apex code, triggers, Lightning web components, deployments, permissions, and integrations. It traces how a problem moves through the system before suggesting or applying a fix.

In plain words
What is it for?
Use it to investigate Apex test failures, trigger behavior, Lightning web component errors, deployment validation problems, governor-limit exceptions, permission issues, and failed external API calls.
Why use it?
It replaces guesswork with a review of the full cause-and-effect chain, from the user interface or automation through database changes and callbacks. This helps distinguish the root cause from symptoms such as failed tests or deployment errors.

Skill for Claude CodeCodex

Part of the sf-compound-engineering plugin — 68 skills, 2 agents, 1 hook, 2 MCP servers shipped together

not rated 10 today A scan 95 tokens original MIT
View the source file divingsbysangam/salesforce-compound-engineering-plugin
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.

agentmods
npx agentmods add skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-debug
Any agent
npx skills add divingsbysangam/salesforce-compound-engineering-plugin --skill sf-debug
Clone the repo
git clone --depth 1 https://github.com/divingsbysangam/salesforce-compound-engineering-plugin

Made for: Claude Code, Codex.

Or install sf-compound-engineering, the plugin that ships this one along with the rest of its 68 skills, 2 agents, 1 hook, 2 MCP servers.

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 sf-debug

README.md
[![agentmods](https://agentmods.dev/badge/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-debug.svg)](https://agentmods.dev/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-debug)
Your own site
<a href="https://agentmods.dev/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-debug"><img src="https://agentmods.dev/badge/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-debug.svg" alt="Measured on agentmods" height="20"></a>
Per session 95 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 889 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00095 $0.00889
Opus 5 $0.00048 $0.00445
Sonnet 5 $0.00019 $0.00178
Haiku 4.5 $0.00010 $0.00089

Measured 4d ago against content hash 2c9e7dfa1e7a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

sf-debug 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 4d 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.

skills/sf-debug/SKILL.md · 51 lines

How it starts

The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.

sf-debug

Principles enforced: 2 (verifiability), 3 (jagged intelligence). See PRINCIPLES.md.

Persona dispatch. This skill dispatches personas as isolated subagents — see the dispatching-parallel-personas skill for the mechanics (isolated subagents, same-response parallelism, same-file-conflict check). The sf-bug-reproduction-validator (a writer) and any reviewers it spawns live under references/personas/; research personas are referenced from ../sf-plan/references/personas/.

Investigate Salesforce-specific bugs systematically — tracing the full causal chain (UI → Flow → trigger → Apex → DML → callback) before proposing a fix — and optionally implement the fix with test-first discipline.

<feature_description> #$ARGUMENTS </feature_description>

Required reads

Procedure lives in sibling files, not only in this orchestrator:

  • Mandatory debugging gate — read references/mandatory-debugging-gate.md before acting on this section.
  • 3-strikes escalation rule — read references/3-strikes-escalation-rule.md before acting on this section.
  • Defense-in-depth pattern — read references/defense-in-depth-pattern.md before acting on this section.
  • Related — read references/related.md before acting on this section.
  • Pipeline mode — when invoked with mode:pipeline, read references/pipeline-mode.md before mutating.

Iron Law: no fixes without root-cause classification first (references/mandatory-debugging-gate.md).

Mode

Default is interactive. mode:pipeline (set by sf-babysit-pr or sf-lfg) is non-interactive: never ask the user; fix only convergent bugs; return the structured JSON in references/pipeline-mode.md. Status spellings are fixed: fixed-and-pushed | fixed-not-pushed | diagnosed-no-fix | flaky-infra | needs-human.

Salesforce Angle

  • Trigger context awareness: when a bug surfaces in a trigger, identify whether it fires on before insert, after update, after undelete, etc., and whether the same logic must hold across all relevant contexts.

Read the full file on GitHub · 51 lines

Files

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.

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. 4d ago First seen · 51 lines · 95 tokens per session scan A 2c9e7dfa1e7a

Subscribe to this mod's changes

sf-debug is a skill published in the GitHub repository divingsbysangam/salesforce-compound-engineering-plugin (10 stars, last pushed today), licensed MIT. It adds 95 tokens to every session and 889 once invoked, about $0.0005 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-31.

Debugging
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens