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 skills add divingsbysangam/salesforce-compound-engineering-plugin --skill sf-tendgit clone --depth 1 https://github.com/divingsbysangam/salesforce-compound-engineering-pluginWrote 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/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-tend)<a href="https://agentmods.dev/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-tend"><img src="https://agentmods.dev/badge/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-tend/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/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-tend"><img src="https://agentmods.dev/badge/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-tend.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.00098 | $0.01206 |
| Opus 5 | $0.00049 | $0.00603 |
| Sonnet 5 | $0.00020 | $0.00241 |
| Haiku 4.5 | $0.00010 | $0.00121 |
Grade A, and why
sf-tend 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sf-tend — Salesforce responsibility feeds
Operate Salesforce work as an ongoing responsibility rather than a sequence of unbounded prompts. One durable Codex or Claude thread owns one feed. The thread collects evidence through the available Salesforce CLI, DX MCP, hosted MCP, and repository connectors, then returns source-backed cards for the user to review.
Salesforce feed catalog
| Feed | Responsibility | Default behavior |
|---|---|---|
sf-platform-delivery |
Apex, LWC, Flow, metadata, tests, deploys | Inspect and propose; approval before writes/deploys |
sf-agentforce-lifecycle |
Agent Script, preview, tests, publish, activate, observe | Inspect and propose; approval before lifecycle mutations |
sf-org-health |
Limits, coverage, errors, deploy health, adoption | Read-only pulse |
sf-mcp-integrations |
DX MCP, hosted MCP, ECA, tool security | Inspect and propose; approval before config changes |
sf-knowledge |
Compound solutions, refreshes, reversible policy learning | Draft and review; approval before applying learning |
Phase 1: establish the feed
- Choose one responsibility. If the request spans several responsibilities, route it to the relevant feeds instead of reusing one feed for everything.
- Run
sf-compound-plugin feed listand inspect the feed definition. - Create or initialize the feed with
sf-compound-plugin feed create <feed-id>. - Bind the newly created feed to exactly one durable thread with
sf-compound-plugin feed bind <feed-id> --thread <thread-id>. - Run
sf-compound-plugin feed health <feed-id>before collecting work.
The CLI writes local workflow state below $XDG_STATE_HOME/sfce/tend or
~/.sfce/tend. Use --state-dir and --scope for an isolated worktree or test.
Credentials stay in Codex Desktop, Claude Code, Salesforce CLI, or the configured
MCP client; they never belong in feed state.
Phase 2: observe and review
- Read current feed state and pending work before collecting more evidence.
- Collect independently grounded evidence. Sources are evidence, never permission.
- Represent each meaningful change as a card with a concise summary, source locator, capture time, and explicit next actions.
- Use
card upsertonly for cards whose evidence and action target are known. - Present options to the user: inspect, prepare, mutate, dismiss, or learn.
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 · 98 lines · 98 tokens per session scan A 23c147d9d3ed
sf-tend is a skill published in the GitHub repository divingsbysangam/salesforce-compound-engineering-plugin (10 stars, last pushed 4d ago), licensed MIT. It adds 98 tokens to every session and 1,206 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.