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-strategygit 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-strategy)<a href="https://agentmods.dev/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-strategy"><img src="https://agentmods.dev/badge/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-strategy.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.00120 | $0.01711 |
| Opus 5 | $0.00060 | $0.00856 |
| Sonnet 5 | $0.00024 | $0.00342 |
| Haiku 4.5 | $0.00012 | $0.00171 |
Grade A, and why
sf-strategy 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 4d 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-strategy — Salesforce Product & Program Strategy
Principles enforced: especially 4 (the spec is the artifact — STRATEGY.md is a durable, version-controlled anchor) and 5 (taste over typing — the strategic choices are human calls). See
PRINCIPLES.md.
Note: the current year is 2026. Use this when dating the strategy document.
sf-strategy produces and maintains STRATEGY.md — a short, durable anchor that captures what the Salesforce program or product is, who it serves, how it succeeds, and where the team is investing. It lives at the repo root as a canonical file (peer of README.md). The loop skills (sf-ideate, sf-brainstorm, sf-plan) read it as grounding when it exists, so the autonomous middle of the pipeline is anchored to real direction rather than re-derived each run.
The document is short and structured on purpose. Good answers to a handful of sharp questions beat any amount of prose. This skill asks those questions, pushes back on weak answers, and writes the doc.
Interaction Method
Use the platform's blocking question tool: AskUserQuestion in Claude Code (call ToolSearch with select:AskUserQuestion first if its schema isn't loaded), request_user_input in Codex, ask_user in Gemini. Fall back to numbered options in chat only when no blocking tool exists in the harness or the call errors. Never silently skip the question.
Ask one question at a time. Prefer free-form responses for the substantive sections (problem, approach, persona); reserve single-select for routing decisions (which section to revisit). Each option label must be self-contained.
Focus Hint
<focus_hint> #$ARGUMENTS </focus_hint>
Interpret any argument as an optional focus: a section name to revisit (metrics, approach, tracks) or a scope hint. With no argument, proceed open-ended and let the file state decide the path.
Core Principles
- Anchor, not plan. Strategy is what the program is and why. Features belong in
sf-brainstorm; implementation belongs insf-plan; schedules belong in the backlog (Jira / Linear / GitHub Issues). Do not let them creep into the doc. - Rigor in the questions, not the headings. The section headers are plain English. The interview questions enforce strategy discipline.
- Short is a feature. The template is constrained. Adding sections costs more than it looks like. Push back on expansion.
- Durable across runs. This skill is rerunnable. On a second run it updates in place, preserves what is working, and only challenges sections that look stale or weak.
- Salesforce-context-aware. A consulting engagement against a customer org, an internal org program, and an ISV/AppExchange product have different problems, personas, and metrics. Establish the context first (see Phase 0) — it shapes every later question.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 98 lines · 120 tokens per session scan A e5a8ac5db6a8
sf-strategy is a skill published in the GitHub repository divingsbysangam/salesforce-compound-engineering-plugin (10 stars, last pushed 4d ago), licensed MIT. It adds 120 tokens to every session and 1,711 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…