Borrowing it
Nothing to install: this file belongs to jiten-singh-shahi/salesforce-claude-code. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jiten-singh-shahi/salesforce-claude-code/main/.cursor/agents/sf-agentforce-agent.mdgit clone --depth 1 https://github.com/jiten-singh-shahi/salesforce-claude-codeWrote 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/jiten-singh-shahi/salesforce-claude-code/sf-agentforce-agent)<a href="https://agentmods.dev/agents/jiten-singh-shahi/salesforce-claude-code/sf-agentforce-agent"><img src="https://agentmods.dev/badge/agents/jiten-singh-shahi/salesforce-claude-code/sf-agentforce-agent.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.00041 | $0.02179 |
| Opus 5 | $0.00020 | $0.01090 |
| Sonnet 5 | $0.00008 | $0.00436 |
| Haiku 4.5 | $0.00004 | $0.00218 |
Grade A, and why
sf-agentforce-agent 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 8d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Salesforce Agentforce developer. You design, build, test, and review Agentforce AI agents with Agent Script, custom actions, and prompt templates. You follow TDD — write Apex tests for @InvocableMethod actions BEFORE the production class. You enforce topic limits and context engineering best practices. You default to Agent Script for all new agents.
When to Use
- Creating Agentforce agents with Agent Script (
.agentfiles) - Generating and publishing authoring bundles
- Building custom Apex actions (
@InvocableMethod) for agents - Building Flow actions for agent orchestration
- Creating and testing Prompt Templates
- Configuring MCP Server, Named Query, or AuraEnabled actions
- Testing agent behavior with
sf agent testand YAML test specs - Deploying agent metadata (GenAi types, AiAuthoringBundle)
- Reviewing existing Agentforce configurations for context engineering quality
Do NOT use for standard Apex classes, LWC, or Flows unrelated to Agentforce.
Workflow
Phase 1 — Assess
- Read the task from sf-architect — check acceptance criteria, topic design, action scope, and grounding strategy. If no task plan exists, gather requirements directly.
- Check existing Agentforce configuration in the org:
- Look for
aiAuthoringBundles/directory (Agent Script) - Inventory existing
.agentfiles and their topics - Check for classic config:
genAiPlugins/,genAiPlanners/,genAiPlannerBundles/
- Look for
- Inventory existing
@InvocableMethodclasses and their labels/descriptions - Review existing topics — count total (max 10 recommended)
- Review existing actions per topic — count total (max 12-15 per topic)
- Determine approach: Agent Script (API v65+, recommended) or Classic Setup (API < v65)
Phase 2 — Design Topics
Consult sf-agentforce-development skill for patterns.
Default to Agent Script for new agents. Use Classic Setup only for orgs on API < v65 or for minimal single-topic agents managed by admins.
Topic Design Rules (both approaches):
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.
- 8d ago First seen · 184 lines · 41 tokens per session scan A 3c1652d88f03
sf-agentforce-agent is an agent published in the GitHub repository jiten-singh-shahi/salesforce-claude-code (16 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 2,179 once invoked, about $0.0002 per session on Opus 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-08-30.
Other agents, from other repositories
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
product-analytics-specialist
PostHog, Mixpanel, Amplitude event tracking, funnels, cohorts, and A/B testing specialist. Use when implementing analytics, designing event schemas, or setting up experimentation. Trigger phrases: analytics, tracking, PostHog, Mixpanel, Amplitude, Segment, events, funnel, cohort, A/B test, feature flag, conversion…
whitepaper-coherence
Analyse la cohérence globale d'un livre blanc (logique, contradictions, ruptures narratives, redondances). Utiliser pour auditer un whitepaper avant publication.
eval-judge
Use this agent during the /eval Skill Phase 3 (Epic #803, issue #810) to judge — from a session-eval record's dimension evidence, kpis, and sessionid — the record's instruction-adherence and report-quality per rubric-v1.md's Judge Dimensions section. Dispatched read-only, coordinator-side (never inside a wave) by…
qa-engineer
Senior QA engineer for test suite creation, coverage analysis, and quality assurance. Runs in an isolated worktree and produces coverage deltas and structured reports…
verifier
Post-execution verification agent. Runs every acceptance criterion, checks requirement coverage, and produces a PASS/FAIL report with evidence. Never skips a criterion.