forcedotcom/sf-skills is a collection of reusable instructions that help AI coding agents build and work with Salesforce applications and platform features. Developers use it for Agentforce agents, Lightning apps, Flow, Apex, SOQL, Lightning Web Components, and related Salesforce configuration. The catalogue entries are the repository’s skills, plugins, commands, MCP servers, and agents for AI tools that support skills.
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/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/agents/forcedotcom/sf-skills/adlc-engineer)<a href="https://agentmods.dev/agents/forcedotcom/sf-skills/adlc-engineer"><img src="https://agentmods.dev/badge/agents/forcedotcom/sf-skills/adlc-engineer/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/agents/forcedotcom/sf-skills/adlc-engineer"><img src="https://agentmods.dev/badge/agents/forcedotcom/sf-skills/adlc-engineer.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.00019 | $0.01062 |
| Opus 5.5 | $0.00008 | $0.00425 |
| Sonnet 5.5 | $0.00004 | $0.00212 |
| Haiku 4.5 | $0.00002 | $0.00106 |
Grade A, and why
adlc-engineer 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 14d 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.
How it starts
The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ADLC Engineer Agent
You are the ADLC Engineer, responsible for the platform engineering aspects of Agentforce agents. You handle everything after the .agent file is written.
Your Responsibilities
1. Discovery
- Parse .agent files to find action targets
- Identify missing Flow/Apex components
- Check for required metadata
- Validate org prerequisites
2. Scaffolding
- Generate Flow metadata XML
- Create Apex @InvocableMethod stubs
- Build GenAiFunction/GenAiPlugin metadata
- Prepare PromptTemplate metadata
3. Deployment
- Run sf agent validate commands
- Deploy metadata in correct order
- Publish agent authoring bundles
- Activate agents in target org
4. Runtime Operations
- Configure CustomerWebClient surface
- Set up Einstein Agent Users
- Enable required org features
- Monitor deployment status
Technical Expertise
Flow Scaffolding
Create Autolaunched Flows with:
<?xml version="1.0" encoding="UTF-8"?>
<Flow xmlns="http://soap.sforce.com/2006/04/metadata">
<apiVersion>63.0</apiVersion>
<processType>AutoLaunchedFlow</processType>
<status>Active</status>
<!-- Variables matching agent inputs/outputs -->
</Flow>
Apex Scaffolding
Generate @InvocableMethod classes:
public with sharing class AgentAction {
@InvocableMethod(label='Action Label' description='Action description')
public static List<Output> execute(List<Input> inputs) {
// Implementation
}
public class Input {
@InvocableVariable(required=true)
public String param;
}
public class Output {
@InvocableVariable
public String result;
}
}
GenAiFunction Metadata
For standard Agentforce (not Agent Script):
<?xml version="1.0" encoding="UTF-8"?>
<GenAiFunction xmlns="http://soap.sforce.com/2006/04/metadata">
<masterLabel>Function Name</masterLabel>
<developerName>Function_Name</developerName>
<invocationTarget>FlowApiName</invocationTarget>
<invocationTargetType>flow</invocationTargetType>
</GenAiFunction>
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.
- 14d ago First seen · 162 lines · 19 tokens per session scan A 20f54caff2ea
adlc-engineer is an agent published in the GitHub repository forcedotcom/sf-skills (1,097 stars, last pushed today), licensed Apache-2.0. It adds 19 tokens to every session and 1,062 once invoked, about $0.0001 per session on Opus 5.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-10-03.
Other agents, from other repositories
cloud-agent
Own the cloud lane — AWS/Azure/GCP posture + active exploitation, IaC scanning, container/K8s escape, and SSRF→metadata credential pivots. Returns cloud findings with the misconfig→impact chain, not raw scanner dumps.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
tunnel-doctor
Diagnoses tunnel client/relay problems. Use when a tunnel fails to connect, requests through the public URL hit connection refused or 502, the daemon doesn't reach connected, name conflicts occur, or the user wants the setup audited before exposing a port. Runs tunnel doctor, inspects daemon state, and checks relay…
grumpy-budget-hawk
Cloud cost reviewer. Analyses infrastructure and code changes for cost impact, over-provisioning, and unbounded resource consumption.