Manage the full lifecycle of Salesforce Agentforce agents: author .agent files from requirements, scaffold and deploy metadata bundles, run security tests against OWASP LLM Top 10 threats, execute structured test suites with session trace analysis, and optimize agent behavior — all coordinated through a plan-mode orchestrator with safeguards against destructive database commands.
Writes Agentforce Agent Script (.agent) files from requirements
Platform engineer — scaffolds Flow/Apex metadata and deploys agent bundles
Plan-mode orchestrator for the Agent Development Life Cycle
Tests Agentforce agents and optimizes based on session trace analysis
Build, modify, debug, and deploy agents with Agentforce Agent Script. TRIGGER when: user creates, modifies, or asks about .agent files or aiAuthoringBundle metadata; changes agent behavior, responses, or conversation logic; designs agent actions, tools, subagents, or flow control; writes or reviews an Agent Spec; previews, debugs, deploys, publishes, or tests agents; uses Agent Script CLI commands (sf agent generate/preview/publish/test). DO NOT TRIGGER when: Apex development, Flow building, Prompt Template authoring, Experience Cloud configuration, or general Salesforce CLI tasks unrelated to Agent Script.
Analyze production Agentforce agent behavior using session traces and Data Cloud. TRIGGER when: user queries STDM session data or Data Cloud trace records; investigates production agent failures, regressions, or performance issues; asks about session traces, conversation logs, or agent metrics; wants to reproduce a reported production issue in preview; runs findSessions or trace analysis queries. DO NOT TRIGGER when: user creates, modifies, or debugs .agent files during development (use developing-agentforce); writes or runs test specs (use testing-agentforce); uses sf agent preview for local development iteration; deploys or publishes agents.
Run OWASP LLM Top 10 security assessments against live Agentforce agents. TRIGGER when: user asks for security testing, OWASP scan, red-teaming, penetration testing, security grade, vulnerability assessment, prompt injection test, data leakage test, excessive agency test, security posture check, or hardening recommendations. DO NOT TRIGGER when: user runs functional smoke tests or batch tests (use testing-agentforce); performs static safety review of .agent file content (use developing-agentforce Section 15); analyzes production session traces (use observing-agentforce); writes or modifies .agent files.
Write, run, and analyze structured test suites for Agentforce agents. TRIGGER when: user writes or modifies test spec YAML (AiEvaluationDefinition); runs sf agent test create, run, run-eval, or results commands; asks about test coverage strategy, metric selection, or custom evaluations; interprets test results or diagnoses test failures; asks about batch testing, regression suites, or CI/CD test integration. DO NOT TRIGGER when: user creates, modifies, previews, or debugs .agent files (use developing-agentforce); deploys or publishes agents; writes Agent Script code; uses sf agent preview for development iteration; analyzes production session traces (use observing-agentforce); requests OWASP, security, or red-team testing (use securing-agentforce).
Executes bash commands
Hook triggers when Bash tool is used
Modifies files
Hook triggers on file write and edit operations
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Uses power tools
Uses Bash, Write, or Edit tools
Uses power tools
Uses Bash, Write, or Edit tools
Agent Development Life Cycle — Build, deploy, test, and optimize Agentforce agents using Claude Code skills and Agent Script DSL.
agentforce-adlc provides a complete set of Claude Code skills for the full Agentforce agent lifecycle — from requirements to production optimization. Claude writes .agent files directly using the Agent Script DSL.
.agent files natively, not via markdown-to-agent conversionUser prompt
| /developing-agentforce
v
+--------------------------+
| Safety Review (Phase 0) |<-- LLM-driven, 7 categories
| .agent file generated |
+--------+-----------------+
| /developing-agentforce (discover)
v
+--------------------------+
| Check org for targets |--missing--> scaffold stubs
+--------+-----------------+
| /developing-agentforce (deploy)
v
+--------------------------+
| Safety Gate -> Validate |<-- Pre-publish check
| -> Publish -> Activate |
+--------+-----------------+
| /testing-agentforce
v
+--------------------------+
| Preview + Batch tests |<-- Safety probe utterances (adversarial)
| + Action execution |
+--------+-----------------+
| /observing-agentforce
v
+--------------------------+
| STDM session analysis |<-- Safety issue detection in traces
| -> Reproduce -> Improve |
+--------------------------+
Each skill can be invoked independently. Run /testing-agentforce on an existing agent without touching the development steps. Run /observing-agentforce on production session data without redeploying.
# Clone the repo
git clone https://github.com/SalesforceAIResearch/agentforce-adlc.git
# Option A: Load directly (development)
claude --plugin-dir ./agentforce-adlc
# Option B: Install via marketplace
claude plugin marketplace add SalesforceAIResearch/agentforce-adlc
claude plugin install agentforce-adlc@agentforce-adlc
When installed as a plugin, skills are namespaced: /agentforce-adlc:developing-agentforce, /agentforce-adlc:testing-agentforce, /agentforce-adlc:observing-agentforce.
# One-command install
curl -sSL https://raw.githubusercontent.com/SalesforceAIResearch/agentforce-adlc/main/tools/install.sh | bash
# Or from local clone
python3 tools/install.py # Auto-detects Claude Code / Cursor
python3 tools/install.py --target cursor # Cursor only
# Plugin management
claude plugin list # List installed plugins
claude plugin update agentforce-adlc@agentforce-adlc # Update plugin
claude plugin uninstall agentforce-adlc@agentforce-adlc # Remove plugin
# File-copy management (legacy)
python3 ~/.claude/adlc-install.py --status
python3 ~/.claude/adlc-install.py --update
python3 ~/.claude/adlc-install.py --uninstall
After install, restart your IDE. Skills are available in any project.
| Component | Plugin (Claude Code) | File-copy (~/.claude/) | File-copy (~/.cursor/) |
|---|---|---|---|
| Skills | Auto-discovered from skills/ | skills/*-agentforce/ | skills/*-agentforce/ |
| Agents | Auto-discovered from agents/ | agents/adlc-*.md | N/A |
| Hooks | Via hooks/hooks.json | hooks/scripts/adlc-*.py | N/A |
| Settings | settings.json (default agent) | settings.json entries | N/A |
Plugin installation is self-contained — no files are copied to ~/.claude/. The file-copy installer is for Cursor and legacy Claude Code setups.
python3 --version. If older, upgrade: brew install [email protected] (macOS) / sudo apt install python3.13 (Ubuntu) / python.org (Windows)sf) v2.x — install guide~/.claude/) or Cursor (~/.cursor/) — at least one must be installed/developing-agentforce)This single skill handles the full development workflow — authoring, discovery, scaffolding, and deployment:
npx claudepluginhub salesforceairesearch/agentforce-adlc --plugin agentforce-adlcAgentforce Agent Development Life Cycle — author, discover, scaffold, deploy, test, and optimize .agent files
Claude Agent SDK Development Plugin
Claude Code skill pack for Salesforce (30 skills)
Hephaestus meta-agent team for creating Agentlas agents and teams, packaging existing agents, and opening the local ontology GUI.
Scaffold, develop, evaluate, and deploy AI agents with Google ADK. Bundles 7 skills for the agent development lifecycle.
Agents for content marketing, customer support, and sales automation