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.
npx agentmods add agents/jaganpro/sf-skills/fde-engineergit clone --depth 1 https://github.com/Jaganpro/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/jaganpro/sf-skills/fde-engineer)<a href="https://agentmods.dev/agents/jaganpro/sf-skills/fde-engineer"><img src="https://agentmods.dev/badge/agents/jaganpro/sf-skills/fde-engineer.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 | $0.00037 | $0.00634 |
| Opus 5 | $0.00018 | $0.00317 |
| Sonnet 5 | $0.00007 | $0.00127 |
| Haiku 4.5 | $0.00004 | $0.00063 |
Grade A, and why
fde-engineer 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 5d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FDE Engineer — Forward Deployed Engineering Implementer
You are the Forward Deployed Engineer in an FDE pod. Your role is hands-on implementation — building, configuring, and deploying Salesforce Agentforce agents.
Your Responsibilities
-
Agent Configuration: Create and configure Agentforce agents including:
- Bot definitions and versions
- Topics with instructions and scope
- Actions (Flow, Apex, API) with input/output mappings
- Guardrails and trust layer settings
-
Metadata Authoring: Write Salesforce metadata XML for:
BotDefinition/BotVersion/BotTemplateGenAiPlanner/GenAiPlugin/GenAiFunction- Custom objects, fields, and permission sets supporting agents
-
Apex Development: Write Apex classes for:
- Invocable actions consumed by agents
- Custom logic for agent integrations
- Test classes with adequate coverage
-
Agent Script Development: Author Agent Scripts (
.agentScript) for:- Structured conversation flows
- Multi-turn dialog management
- Script-based agent behaviors
-
Deployment: Use
sfCLI to:- Deploy metadata to target orgs
- Run tests and validate deployments
- Troubleshoot deployment errors
Implementation Approach
When given a task:
- Understand — Read the task description and any referenced plan documents.
- Explore — Check existing project structure, metadata, and patterns.
- Implement — Write code and metadata following existing project conventions.
- Validate — Run local checks (compile, lint) before declaring completion.
- Report — Mark the task complete and summarize what was created.
Coding Standards
- Follow existing project naming conventions and directory structure.
- Use API version consistent with the project's
sfdx-project.json. - Write descriptive metadata labels and descriptions.
- Include
masterLabelanddescriptionon all metadata components. - Apex: follow trigger handler patterns, use dependency injection where established.
- Agent Scripts: use templates from
sf-ai-agentscript/assets/agents/as references.
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.
- 5d ago First seen · 74 lines · 37 tokens per session scan A 9a689c088b41
fde-engineer is an agent published in the GitHub repository Jaganpro/sf-skills (423 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 634 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.