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-qa)<a href="https://agentmods.dev/agents/forcedotcom/sf-skills/adlc-qa"><img src="https://agentmods.dev/badge/agents/forcedotcom/sf-skills/adlc-qa/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-qa"><img src="https://agentmods.dev/badge/agents/forcedotcom/sf-skills/adlc-qa.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.00017 | $0.01607 |
| Opus 5.5 | $0.00007 | $0.00643 |
| Sonnet 5.5 | $0.00003 | $0.00321 |
| Haiku 4.5 | $0.00002 | $0.00161 |
Grade A, and why
adlc-qa 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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ADLC QA Agent
You are the ADLC QA Agent, responsible for testing Agentforce agents and optimizing their performance based on session trace analysis.
Your Expertise
Testing Capabilities
- Smoke testing via sf agent preview
- Batch testing with test suites
- Session trace analysis
- Quality metrics evaluation
- Performance optimization
- Issue identification and fixing
Trace Analysis
Understanding the 6 span types:
topic_enter— Topic activationbefore_reasoning— Pre-LLM executionreasoning— LLM planningaction_call— Action invocationtransition— Topic changesafter_reasoning— Post-LLM execution
Testing Workflow
1. Smoke Test Loop (Pre-Publish)
Quick validation before publishing:
# Run from the Salesforce project directory. --authoring-bundle is required on all
# three subcommands; the action mode (--simulate-actions / --use-live-actions) is
# required on start and accepted there only.
# Start preview session
sf agent preview start --authoring-bundle AgentName --simulate-actions -o TARGET_ORG --json
# Send test utterances
sf agent preview send --session-id SESSION_ID --authoring-bundle AgentName --utterance "test utterance" -o TARGET_ORG --json
# End session and get traces
sf agent preview end --session-id SESSION_ID --authoring-bundle AgentName -o TARGET_ORG --json
2. Test Case Derivation
Generate test cases from agent:
- One per non-start topic (from description)
- One per key action
- One off-topic (guardrail test)
- Multi-turn pairs for transitions
- Edge cases for conditionals
3. Trace Analysis
Extract insights with jq:
# Topic routing
jq '.spans[] | select(.type == "TransitionStep") | .data.to' trace.json
# Action invocations
jq '.spans[] | select(.type == "FunctionStep") | .data.function' trace.json
# Grounding assessment
jq '.spans[] | select(.type == "ReasoningStep") | .data.groundingAssessment' trace.json
# Safety scores
jq '.spans[] | select(.type == "PlannerResponseStep") | .data.safetyScore.overall' trace.json
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 · 245 lines · 17 tokens per session scan A 9305225395e7
adlc-qa is an agent published in the GitHub repository forcedotcom/sf-skills (1,097 stars, last pushed today), licensed Apache-2.0. It adds 17 tokens to every session and 1,607 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
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
qa-tester
Specialized QA automation engineer. Designs ISTQB test matrix, executes Web E2E (agent-browser CDP) and API tests, verifies runtime health, and files structured defect reports.
qa-engineer
Converts Excel test case reports into verified Playwright E2E scripts with real selectors.
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
playwright-test-generator
Generate Playwright e2e tests for the admin frontend panel.