Ext Ops Panel
Open dashboard

What it can do: salesforce-claude-code

Plugin bundle · jiten-singh-shahi

What salesforce-claude-code declares, asks for and runs, according to the marketplaces we read. Installs into the AI tool as a plugin bundle; what it starts is listed below. None of the marketplaces we read publishes its tools or the settings it asks for. As of our marketplace pass on 2026-10-13.

This is not a security audit. We list what the marketplaces publish about this plugin: what it declares, what it asks for and what it runs. We do not run or inspect its code, and a verified mark is the marketplace's statement, not ours.

Where it runs

  • Installs into the AI tool as a plugin bundle; what it starts is listed below.As declared on: Claude Code: claude-plugins-community.

What it declares

None of the marketplaces we read publishes a list of tools for it.

Prompts and resources: the marketplaces we read do not publish them.

What it asks for

None of the marketplaces we read lists environment variables for it.

Names only: we keep no values, examples or descriptions of these variables. OAuth scopes and install-time settings are not published by the marketplaces we read.

What it runs besides MCP

Skills: 58 As declared on: Claude Code: claude-plugins-community.

  • aside
  • checkpoint
  • configure-scc
  • continuous-agent-loop
  • mcp-server-patterns
  • model-route
  • prompt-optimizer
  • refactor-clean
  • resume-session
  • save-session
  • search-first
  • security-scan
Show the remaining 46
  • sessions
  • sf-2gp-security-review
  • sf-agentforce-development
  • sf-agentforce-mcp-actions
  • sf-apex-async-patterns
  • sf-apex-best-practices
  • sf-apex-constraints
  • sf-apex-cursor
  • sf-apex-enterprise-patterns
  • sf-apex-testing
  • sf-api-design
  • sf-approval-processes
  • sf-aura-development
  • sf-build-fix
  • sf-cli-reference
  • sf-data-modeling
  • sf-debugging
  • sf-deployment
  • sf-deployment-constraints
  • sf-devops-ci-cd
  • sf-docs-lookup
  • sf-e2e-testing
  • sf-experience-cloud
  • sf-flow-development
  • sf-governor-limits
  • sf-harness-audit
  • sf-help
  • sf-integration
  • sf-lwc-constraints
  • sf-lwc-development
  • sf-lwc-testing
  • sf-metadata-management
  • sf-platform-events-cdc
  • sf-quickstart
  • sf-security
  • sf-security-constraints
  • sf-soql-constraints
  • sf-soql-optimization
  • sf-tdd-workflow
  • sf-testing-constraints
  • sf-trigger-constraints
  • sf-trigger-frameworks
  • sf-visualforce-development
  • strategic-compact
  • update-docs
  • update-platform-docs

Agents: 17 As declared on: Claude Code: claude-plugins-community.

  • deep-researcher
  • doc-updater
  • eval-runner
  • learning-engine
  • loop-operator
  • refactor-cleaner
  • sf-admin-agent
  • sf-agentforce-agent
  • sf-apex-agent
  • sf-architect
  • sf-aura-reviewer
  • sf-bugfix-agent
Show the remaining 5
  • sf-flow-agent
  • sf-integration-agent
  • sf-lwc-agent
  • sf-review-agent
  • sf-visualforce-reviewer

Hooks: 7 As declared on: Claude Code: claude-plugins-community.

  • PostToolUse
  • PostToolUseFailure
  • PreCompact
  • PreToolUse
  • SessionEnd
  • SessionStart
  • Stop

Who answers for it

jiten-singh-shahi

  • No marketplace we read marks it or its publisher as verified.
  • License: MIT.
  • The repository github.com/jiten-singh-shahi/salesforce-claude-code belongs to the account the publisher is listed under on Claude Code: claude-plugins-community.

How it has changed

Its tools, settings, hooks and composition have not changed since we started watching it.

In context

  • Median number of secrets a plugin bundle asks for on the marketplaces we read: 0.0. This one asks for: 0.
  • Share of plugin bundles that run on a remote server: 20%.

Where it is published and how its figures have moved

Compare it side by side with similar plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built