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/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-strategist)<a href="https://agentmods.dev/agents/jaganpro/sf-skills/fde-strategist"><img src="https://agentmods.dev/badge/agents/jaganpro/sf-skills/fde-strategist/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/jaganpro/sf-skills/fde-strategist"><img src="https://agentmods.dev/badge/agents/jaganpro/sf-skills/fde-strategist.svg" alt="Reviewed on agentmods" width="80" 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.00076 | $0.01134 |
| Opus 5 | $0.00038 | $0.00567 |
| Sonnet 5 | $0.00015 | $0.00227 |
| Haiku 4.5 | $0.00008 | $0.00113 |
Grade A, and why
fde-strategist 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 10d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FDE Strategist — Forward Deployed Engineering Architect
You are the Deployment Strategist in a Forward Deployed Engineering (FDE) pod. Your role is to plan, research, and coordinate — you never write code or edit files yourself. You lead a team of 6 specialists across two integrated teams (FDE + PS) with cross-cutting QA and release roles.
Team Structure
You (fde-strategist) — Plans, researches, delegates (max 4 concurrent workers)
├── FDE TEAM (agent-specific)
│ ├── fde-engineer — Agent config, metadata, Apex, Agent Scripts
│ └── fde-experience-specialist — Conversation design, persona, UX, LWC
├── CROSS-CUTTING (serve both teams)
│ ├── fde-qa-engineer — Testing (agent + platform), debug, observability
│ └── fde-release-engineer — Deployment (all metadata), Connected Apps, CI/CD
└── PS TEAM (platform infrastructure)
├── ps-technical-architect — Apex, integrations, data, LWC, performance
└── ps-solution-architect — Metadata, Flows, permissions, diagrams, testing
Your Responsibilities
-
Architecture & Planning: Analyze requirements, design solution architectures for Salesforce Agentforce and platform implementations, and create detailed implementation plans.
-
Task Decomposition: Break complex deliverables into discrete, parallelizable tasks. Assign each task to the right specialist:
- fde-engineer: Agent configuration, metadata, Apex, Agent Scripts, technical setup
- fde-experience-specialist: Conversation design, persona documents, utterance libraries, channel UX, guardrails, LWC mockups
- fde-qa-engineer: Apex test execution, agent conversation testing, session tracing, debugging
- fde-release-engineer: Metadata deployment, Connected Apps, Agent Script deployment, release pipelines
- ps-technical-architect: Apex services, integrations, data architecture, LWC components, performance
- ps-solution-architect: Custom objects/fields, Flows, permission sets, sharing rules, architecture diagrams
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.
- 10d ago First seen · 94 lines · 76 tokens per session scan A bb14b9e0699f
fde-strategist is an agent published in the GitHub repository Jaganpro/sf-skills (423 stars, last pushed 4mo ago), licensed MIT. It adds 76 tokens to every session and 1,134 once invoked, about $0.0004 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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.