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.
npx skills add forcedotcom/sf-skills --skill dx-code-analyzer-configuregit clone --depth 1 https://github.com/forcedotcom/sf-skillsWrote 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/skills/forcedotcom/sf-skills/dx-code-analyzer-configure)<a href="https://agentmods.dev/skills/forcedotcom/sf-skills/dx-code-analyzer-configure"><img src="https://agentmods.dev/badge/skills/forcedotcom/sf-skills/dx-code-analyzer-configure.svg" alt="Measured on agentmods" 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.00226 | $0.05596 |
| Opus 5 | $0.00113 | $0.02798 |
| Sonnet 5 | $0.00045 | $0.01119 |
| Haiku 4.5 | $0.00023 | $0.00560 |
Grade A, and why
dx-code-analyzer-configure scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- tool: ["curl"] How it starts
The opening of the file, as written. The whole thing — 502 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configuring Code Analyzer Skill
Overview
Ecosystem: This skill is part of a 3-skill Code Analyzer suite —
dx-code-analyzer-run(scans & results) ·dx-code-analyzer-configure(setup, config, CI/CD) ·dx-code-analyzer-custom-rule-create(custom rule authoring).
This skill manages the code-analyzer.yml configuration file — the single source of truth for how Code Analyzer behaves in a project. All customization (engines, rules, ignores, suppressions) is done by creating or editing this file. If the file doesn't exist, this skill creates it in the current working directory.
Scope
In scope:
- Checking prerequisites (sf CLI, Java, Node.js, Python, org auth)
- Installing/updating the Code Analyzer plugin
- Creating
code-analyzer.ymlif it doesn't exist - Editing
code-analyzer.ymlfor all configuration changes - Engine settings, rule overrides, ignore patterns, suppressions
- CI/CD pipeline setup (GitHub Actions, Jenkins, etc.)
- Environment validation and troubleshooting
Out of scope:
- Running scans → use
dx-code-analyzer-runskill - Fixing violations, explaining rules, suppression management → use
dx-code-analyzer-runskill - Creating custom rules → use
dx-code-analyzer-custom-rule-createskill
Tool Usage Rules
Allowed: Bash (sf, java, node, python3, npm), Read, Write, Edit
Forbidden: MCP tools, Agent tool, Web tools, other skills, which, find, locate, searching for binaries
Core Principle: YAML Only When Customizing
Code Analyzer works out of the box with NO config file — all defaults are built into the tool. The code-analyzer.yml file is ONLY created when the user explicitly requests a customization.
Rules:
- Do NOT create
code-analyzer.ymlproactively — only when user asks to change something - Do NOT duplicate built-in defaults — only write entries that intentionally override behavior
- Always place at project root — where
sfdx-project.jsonorsf-project.jsonlives - The CLI auto-discovers it —
sf code-analyzer runfrom project root automatically picks upcode-analyzer.ymlin that directory. No--config-fileflag needed. - User says "configure code analyzer" with no specifics? → Ask what they want to customize. Don't create an empty or boilerplate file.
What ships with it
13 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.
- examples/apex-project-config.yml 1.2 KB
- examples/ci-github-actions.yml 2.5 KB
- examples/fullstack-project-config.yml 1.3 KB
- examples/lwc-project-config.yml 772 B
- references/ci-cd-templates.md 23 KB
- references/config-schema.md 6.7 KB
- references/diagnostic-flow.md 3.1 KB
- references/engine-prerequisites.md 5.1 KB
- references/rule-name-resolution.md 3.1 KB
- references/troubleshooting.md 7.3 KB
- scripts/check-prerequisites.sh 6.2 KB runs code
- scripts/generate-config.sh 3.7 KB runs code
- scripts/validate-config.sh 5.1 KB runs code
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.
- 3d ago First seen · 502 lines · 226 tokens per session scan A b4392b7dd5ea
dx-code-analyzer-configure is a skill published in the GitHub repository forcedotcom/sf-skills (966 stars, last pushed yesterday), licensed Apache-2.0. It adds 226 tokens to every session and 5,596 once invoked, about $0.0011 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-cache
Atmos caching: CI cache configuration and commands, GitHub Actions cache integration, Terraform registry cache mirror/list/prune/stats/trust, and cache modernization guidance.
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.