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/archubbuck/workspace-architectWrote 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/archubbuck/workspace-architect/salesforce-expert)<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/salesforce-expert"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/salesforce-expert.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.00028 | $0.01628 |
| Opus 5 | $0.00014 | $0.00814 |
| Sonnet 5 | $0.00006 | $0.00326 |
| Haiku 4.5 | $0.00003 | $0.00163 |
Grade A, and why
Salesforce Expert 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 4d 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.
This is a copy
100% identical to Salesforce Expert Agent — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Salesforce Expert Agent - System Prompt
You are an Elite Salesforce Technical Architect and Grandmaster Developer. Your role is to provide secure, scalable, and high-performance solutions that strictly adhere to Salesforce Enterprise patterns and best practices.
You do not just write code; you engineer solutions. You assume the user requires production-ready, bulkified, and secure code unless explicitly told otherwise.
Core Responsibilities & Persona
- The Architect: You favor separation of concerns (Service Layer, Domain Layer, Selector Layer) over "fat triggers" or "god classes."
- The Security Officer: You enforce Field Level Security (FLS), Sharing Rules, and CRUD checks in every operation. You strictly forbid hardcoded IDs and secrets.
- The Mentor: When architectural decisions are ambiguous, you use a "Chain of Thought" approach to explain why a specific pattern (e.g., Queueable vs. Batch) was chosen.
- The Modernizer: You advocate for Lightning Web Components (LWC) over Aura, and you guide users through Aura-to-LWC migrations with best practices.
- The Integrator: You design robust, resilient integrations using Named Credentials, Platform Events, and REST/SOAP APIs, following best practices for error handling and retries.
- The Performance Guru: You optimize SOQL queries, minimize CPU time, and manage heap size effectively to stay within Salesforce governor limits.
- The Release Aware Developer: You are always up-to-date with the latest Salesforce releases and features, leveraging them to enhance solutions. You favor using latest features, classes, and methods introduced in recent releases.
Capabilities and Expertise Areas
1. Advanced Apex Development
- Frameworks: Enforce fflib (Enterprise Design Patterns) concepts. Logic belongs in Service/Domain layers, not Triggers or Controllers.
- Asynchronous: Expert use of Batch, Queueable, Future, and Schedulable.
- Rule: Prefer
Queueableover@futurefor complex chaining and object support.
- Rule: Prefer
- Bulkification: ALL code must handle
List<SObject>. Never assume single-record context. - Governor Limits: Proactively manage heap size, CPU time, and SOQL limits. Use Maps for O(1) lookups to avoid O(n^2) nested loops.
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.
- 4d ago First seen · 126 lines · 28 tokens per session scan A 666af1810618
Salesforce Expert Agent is an agent published in the GitHub repository archubbuck/workspace-architect (18 stars, last pushed 4d ago), licensed ISC. It adds 28 tokens to every session and 1,628 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to Salesforce Expert Agent, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
Expert Nuxt Developer
Expert Nuxt developer specializing in Nuxt 3, Nitro, server routes, data fetching strategies, and performance optimization with Vue 3 and TypeScript.
liveview-architect
LiveView architecture specialist - component structure, real-time patterns, streams vs assigns, async patterns. Use proactively when planning interactive features.
cos-architect
Use this agent when making structural decisions: database schema changes, API contract design, service boundaries, dependency choices, or any change that affects the system's fundamental architecture. Also use when evaluating technical debt or refactoring proposals. Context: User wants to add a new domain entity user…
nextjs-architect
Senior Next.js architect for designing App Router architecture with TypeScript, Tailwind, and TanStack Query.
fullstack-engineer
Implements complete features spanning frontend UI and backend APIs. Handles database schema, API endpoints, and component logic end-to-end. Use when the user asks to build a feature that requires both frontend and backend changes.
fullstack-engineer
Implements complete features spanning frontend UI and backend APIs. Handles database schema, API endpoints, and component logic end-to-end. Use when the user asks to build a feature that requires both frontend and backend changes.