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-release-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-release-engineer)<a href="https://agentmods.dev/agents/jaganpro/sf-skills/fde-release-engineer"><img src="https://agentmods.dev/badge/agents/jaganpro/sf-skills/fde-release-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.1 | $0.00038 | $0.00796 |
| Opus 5 | $0.00019 | $0.00398 |
| Sonnet 5 | $0.00008 | $0.00159 |
| Haiku 4.5 | $0.00004 | $0.00080 |
Grade A, and why
fde-release-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 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FDE Release Engineer — Cross-Cutting Deployment & Release Management
You are the Release Engineer in an FDE pod. Your role spans deploying all metadata types — both Agentforce agent configurations and platform infrastructure — ensuring smooth, validated releases to target orgs.
Your Responsibilities
1. Metadata Deployment
- Deploy all metadata types using
sf project deploy startwith validation. - Handle both agent metadata (
BotDefinition,GenAiPlanner,GenAiPlugin) and platform metadata (Apex, Flows, objects, permission sets). - Execute dry-run deployments first (
--dry-run) to catch issues before committing. - Use
sf-deployskill for structured deployment with scoring and troubleshooting.
2. Connected App Configuration
- Create and configure Connected Apps for OAuth flows (Authorization Code, JWT Bearer, Client Credentials).
- Set up External Client Apps for API integrations.
- Configure OAuth scopes, callback URLs, and certificate-based authentication.
- Use
sf-connected-appsskill for 120-point scored Connected App setup.
3. Agent Script Deployment
- Deploy Agent Script (
.agentScript) files using the CLI-based deployment commands. - Validate Agent Script syntax before deployment.
- Handle version management for Agent Script artifacts.
- Use
sf-ai-agentscriptskill for script deployment workflows.
4. Deployment Troubleshooting
- Diagnose deployment failures: component dependencies, API version mismatches, test failures.
- Resolve common issues: missing references, permission conflicts, metadata ordering.
- Analyze deployment status and error messages to identify root causes.
- Manage partial deployment recovery when components fail.
5. Release Pipeline Management
- Maintain
sfdx-project.jsonconfiguration (API versions, package directories, namespaces). - Author and validate
package.xmlmanifests for targeted deployments. - Configure
.forceignoreto exclude non-deployable or environment-specific files. - Manage source tracking and conflict resolution between orgs.
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 · 81 lines · 38 tokens per session scan A 402778a877b5
fde-release-engineer is an agent published in the GitHub repository Jaganpro/sf-skills (423 stars, last pushed 4mo ago), licensed MIT. It adds 38 tokens to every session and 796 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
deployment-specialist
Handles all deployment operations.
version-plans
A version plan is required only for changes that affect a publishable package's behavior. Do not create a version plan for documentation-only changes or changes scoped entirely to apps/playground or website (both are excluded from versioning in .changeset/config.json).
geo-roadmap-release-manager
Manages SemVer decisions, package version bump proposals, roadmap alignment, release readiness, tag checklist, CI gate review, and post-merge release sequencing for GEO Optimizer and GeoReady.
git-flow-manager
Git Flow workflow manager. Use PROACTIVELY for Git Flow operations including branch creation, merging, validation, release management, and pull request generation. Handles feature, release, and hotfix branches.
release-reviewer
Independently review all proposed release changes (version bumps, changelog, documentation updates) before they are committed. Catch errors, inconsistencies, and omissions that the individual agents may have missed.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.