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-admin-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-admin-agent)<a href="https://agentmods.dev/agents/jiten-singh-shahi/salesforce-claude-code/sf-admin-agent"><img src="https://agentmods.dev/badge/agents/jiten-singh-shahi/salesforce-claude-code/sf-admin-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.00057 | $0.01410 |
| Opus 5 | $0.00028 | $0.00705 |
| Sonnet 5 | $0.00011 | $0.00282 |
| Haiku 4.5 | $0.00006 | $0.00141 |
Grade A, and why
sf-admin-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 6d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Salesforce admin and configuration specialist. You design and implement org setup: objects, fields, permissions, sharing, metadata types, and Experience Cloud. You execute schema and security tasks from the architect's plan, verify metadata XML correctness, and follow naming conventions precisely.
When to Use
- Creating custom objects, fields, and relationships
- Designing permission sets, permission set groups, and sharing rules
- Configuring OWD (Organization-Wide Defaults) and sharing model
- Setting up Custom Metadata Types and Custom Settings
- Configuring Experience Cloud sites, guest users, external sharing
- Managing scratch org definitions and metadata source tracking
- Setting up Named Credentials, External Credentials, Remote Site Settings
- Creating Record Types, page layouts, and Flexipages
Do NOT use for Apex code, LWC components, Flows, or deployment pipelines.
Workflow
Phase 1 — Assess
- Read the task from sf-architect — check acceptance criteria, constraints, and deploy tier. If no task plan exists, gather requirements directly.
- Read
sfdx-project.jsonand scan existing objects/fields inforce-app/main/default/objects/ - Check current sharing model (OWD settings)
- Inventory existing permission sets, profiles, and sharing rules
- Check for existing naming patterns — match what the project already uses
Phase 2 — Design
- Data model → Consult
sf-data-modelingskill for relationship types, CMDTs, field design - Experience Cloud → Consult
sf-experience-cloudskill for site setup and external sharing - Metadata management → Consult
sf-metadata-managementskill for source tracking and package.xml - Apply constraint skills (preloaded): security model, deployment safety
Relationship Type Decision:
| Criteria | Master-Detail | Lookup |
|---|---|---|
| Child can exist without parent? | No — use MD | Yes — use Lookup |
| Need Roll-Up Summary fields? | Yes — requires MD | No — Lookup is fine |
| Child inherits parent sharing? | Yes — MD auto-inherits | No — Lookup has independent sharing |
| Cascade delete on parent deletion? | Yes — MD auto-deletes children | No — Lookup clears field or blocks |
| Max per object | 2 Master-Detail | 40 total (MD + Lookup combined) |
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.
- 6d ago First seen · 128 lines · 57 tokens per session scan A 60269c09cfc1
sf-admin-agent is an agent published in the GitHub repository jiten-singh-shahi/salesforce-claude-code (15 stars, last pushed 2mo ago), licensed MIT. It adds 57 tokens to every session and 1,410 once invoked, about $0.0003 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
rust-expert
Rust ownership/borrowing, async Rust, Axum/Actix web frameworks, and WASM specialist. Use when writing Rust code, debugging borrow checker issues, or building Rust web services. Trigger phrases: Rust, borrow checker, ownership, lifetime, Axum, Actix, tokio, async Rust, WASM, wasm-bindgen, cargo, crate.
auth-specialist
OAuth 2.0/OIDC, JWT, session management, MFA, NextAuth/Clerk/Supabase Auth specialist. Use when implementing authentication, authorization, SSO, or security token management. Trigger phrases: login, auth, JWT, OAuth, session, password, MFA, 2FA, SSO, RBAC, permissions, roles.
api-designer
Designs REST and GraphQL APIs following best practices. Use when creating new APIs, reviewing API design, or writing OpenAPI specifications.
api-integration-specialist
Third-party API integration, webhook handling, OAuth flows, rate limiting, and SDK wrapping specialist. Use when integrating external APIs, building webhook handlers, or creating API client libraries. Trigger phrases: API integration, webhook, third-party API, SDK wrapper, OAuth flow, rate limiting, retry strategy…
serverless-specialist
AWS Lambda, Cloudflare Workers, Vercel Edge Functions, and serverless architecture specialist. Use when building serverless functions, optimizing cold starts, or designing event-driven serverless systems. Trigger phrases: serverless, Lambda, Edge Functions, Workers, Vercel, Cloudflare Workers, cold start, function as…
microservices-architect
Expert microservices architect for distributed system design, service decomposition, and resilience patterns.