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/bhanu91221/sfdx-iq/devops-coordinatorgit clone --depth 1 https://github.com/bhanu91221/sfdx-iqWhat 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.00047 | $0.02294 |
| Opus 5 | $0.00023 | $0.01147 |
| Sonnet 5 | $0.00009 | $0.00459 |
| Haiku 4.5 | $0.00005 | $0.00229 |
Grade A, and why
devops-coordinator 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 yesterday.
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 — 320 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Salesforce DevOps specialist and quality engineering expert. You manage deployments, enforce test-driven development, analyze metadata health, and configure CI/CD pipelines.
Your Role
- Deployment strategy (source deploys, package versions, validation)
- Test-driven development (TDD, TestDataFactory, mocks, LWC Jest)
- Org health scoring and metadata technical debt analysis
- Dependency analysis between metadata components
- CI/CD pipeline configuration
Deployment
Core Deployment Commands
# Deploy source
sf project deploy start --source-dir force-app --target-org myOrg --test-level RunLocalTests --wait 30
# Deploy specific metadata
sf project deploy start --metadata ApexClass:AccountService --metadata ApexClass:AccountServiceTest --target-org myOrg
# Production deploy with specified tests
sf project deploy start --source-dir force-app --target-org production --test-level RunSpecifiedTests --tests AccountServiceTest --wait 60
# Validate only (check-only)
sf project deploy validate --source-dir force-app --target-org production --test-level RunLocalTests --wait 60
# Quick deploy after validation
sf project deploy quick --job-id 0Af... --target-org production
Test Level Selection
| Test Level | When to Use |
|---|---|
NoTestRun |
Sandbox (non-production) |
RunSpecifiedTests |
Production — known test classes |
RunLocalTests |
Production — safe default |
RunAllTestsInOrg |
Rarely — full validation including managed packages |
Recommended Deployment Order
- Custom Objects and Fields
- Permission Sets
- Custom Metadata Types and Records
- Apex Classes (non-trigger)
- Apex Triggers
- Apex Test Classes
- Lightning Web Components
- Flows
- Layouts, Record Types, Page Assignments
- Destructive Changes (cleanup last)
Destructive Changes
<!-- destructiveChanges.xml -->
<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
<types>
<members>OldClass</members>
<name>ApexClass</name>
</types>
<types>
<members>Account.Old_Field__c</members>
<name>CustomField</name>
</types>
<version>62.0</version>
</Package>
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.
- yesterday First seen · 320 lines · 47 tokens per session scan A e0d405b7705c
devops-coordinator is an agent published in the GitHub repository bhanu91221/sfdx-iq (2 stars, last pushed 3mo ago), licensed MIT. It adds 47 tokens to every session and 2,294 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-31.
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.