What is scan-security?

A security scanner for Salesforce projects that checks Apex and configuration files for common access-control and secret-management problems.

It scans a force-app folder, checks SOQL and database operations, reviews callout and configuration settings, and reports findings by severity.

It helps find missing object and field permissions, unsafe sharing, unsecured callouts, and hardcoded secrets before release.

scan-security — Command for Claude Code by BanibrataChatterjee

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/scan-security/github.svg)](https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/scan-security)

Your own site

<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/scan-security"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/scan-security/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/scan-security"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/scan-security.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 441 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00441
Opus 5.5	$0.00000	$0.00176
Sonnet 5.5	$0.00000	$0.00088
Haiku 4.5	$0.00000	$0.00044

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

Security

Grade A, and why

scan-security 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/scan-security.md · 63 lines

What it actually says

Wraps agents/security-scanner/AGENT.md. Walks a force-app/ tree and flags CRUD/FLS, sharing, callout-without-Named-Credential, and hardcoded-secret issues.

Step 1 — Collect inputs

Ask:

1. What scope should be scanned?
   Example: force-app/main/default/

2. Target-org alias? (optional)

3. Severity threshold? (default P2 — show all; use P1 to hide low-severity)

Step 2 — Load the agent

Read agents/security-scanner/AGENT.md in full + every reference under Mandatory Reads Before Starting, especially standards/decision-trees/sharing-selection.md.

Step 3 — Execute

Follow the 6-step plan:

Class-level checks (sharing keyword, unescaped SOQL, callouts, hardcoded secrets)
DML-level checks (CRUD/FLS)
SOQL-level checks (WITH SECURITY_ENFORCED / USER_MODE)
Config-level checks (Remote Sites, debug logs with secrets)
Decision-tree routing for sharing findings
(Optional) validate_against_org lookup for existing SecurityUtils equivalents

Step 4 — Deliver

Summary counts by severity and confidence
Findings table
Per-finding before/after for P0 and P1
Hardcoded-secret summary with [REDACTED] placeholder — never print secret values
Citations

/refactor-apex for classes that need SecurityUtils integrated
/score-deployment before shipping security fixes to production
/request-skill if a finding type has no canonical skill yet

What this command does NOT do

Does not modify any file.
Does not print secret values in the output — always [REDACTED].
Does not replace professional penetration testing.

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.

2mo ago First seen · 63 lines · 0 tokens per session scan A 63754de41904

Subscribe to this mod's changes

scan-security 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 441 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-09-03.