agentmods.dev

sf-ideate

sf-ideate is a skill for Claude Code from divingsbysangam/salesforce-compound-engineering-plugin. It costs 74 tokens per session (630 once invoked), scanned A, original, MIT.

A Salesforce idea-generation skill for exploring improvements to an org, which is a Salesforce environment containing its data and configuration. It produces several ideas grounded in the available code, metadata, strategy, and documented lessons, then critiques them.

In plain words
What is it for?
Use it when deciding what to improve in a Salesforce org, exploring options for existing Apex code, or looking for broader strategic ideas grounded in the current project.
Why use it?
It gives brainstorming a connection to the actual Salesforce system instead of producing disconnected suggestions. Critiquing each idea exposes its supporting evidence and likely weaknesses before someone decides what to build.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions CLAUDE.md; names the AskUserQuestion tool; mentions Claude Code.

Part of the sf-compound-engineering plugin — 68 skills, 1 hook, 2 MCP servers shipped together

not rated 10repo 3d ago A scan 74 tokens original MIT

Good fit Use it when deciding what to improve in a Salesforce org, exploring options for existing Apex code, or looking for broader strategic ideas grounded in the current project.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-ideate
View source ↗ divingsbysangam/salesforce-compound-engineering-plugin
Install

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.

Any agent
npx skills add divingsbysangam/salesforce-compound-engineering-plugin --skill sf-ideate
Clone the repo
git clone --depth 1 https://github.com/divingsbysangam/salesforce-compound-engineering-plugin

Made for: Claude Code.

Or install sf-compound-engineering, the plugin that ships this one along with the rest of its 68 skills, 1 hook, 2 MCP servers.

Wrote 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.

agentmods badge for sf-ideate

README.md
[![agentmods](https://agentmods.dev/badge/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-ideate.svg)](https://agentmods.dev/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-ideate)
Your own site
<a href="https://agentmods.dev/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-ideate"><img src="https://agentmods.dev/badge/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-ideate.svg" alt="Measured on agentmods" height="20"></a>
Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 630 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00074 $0.00630
Opus 5 $0.00037 $0.00315
Sonnet 5 $0.00015 $0.00126
Haiku 4.5 $0.00007 $0.00063

Measured 8d ago against content hash e5178edd8109, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

sf-ideate 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 8d 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.

skills/sf-ideate/SKILL.md · 42 lines

How it starts

The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.

sf-ideate

Principles enforced: especially 5 (taste over typing — deciding what to build is a human call) and 7 (outsource thinking, not understanding). See PRINCIPLES.md.

Strategy grounding: If a STRATEGY.md exists at the repo root, read it first and ground ideas in its target problem, approach, and key metrics. If none exists and the topic is strategic, suggest /sf-strategy.

Generate 3-5 grounded ideas about a Salesforce topic with explicit warrants, then critique each.

<feature_description> #$ARGUMENTS </feature_description>

Salesforce Angle

  • Ideas are grounded in the current org's metadata, Apex code structure, and docs/solutions/ learnings.
  • Surprise mode pulls from cross-domain analogies (other Salesforce orgs, SF community patterns) rather than local repo signals only.

Interaction Method

When asking the user a question, use the platform's blocking question tool (AskUserQuestion in Claude Code, request_user_input in Codex, ask_user in Gemini). Fall back to numbered options in chat when no blocking tool is available. Ask one question at a time. Prefer concise single-select choices when natural options exist.

Procedure

This skill follows the standard sf-compound-engineering execution discipline:

  1. Understand the input — read the <feature_description> block above and any referenced files, plans, or issues.
  2. Plan a small set of phases — break the work into 2-5 ordered steps that an implementer (or another skill) can verify.
  3. Apply the Salesforce Angle notes above — these encode the platform-specific considerations (governor limits, sharing context, deploy ordering, FLS, metadata semantics) that distinguish this skill from generic counterparts.
  4. Use Salesforce-aware contexts and commands — file paths under force-app/main/default/..., test commands like sf apex run test, deploy commands like sf project deploy validate and sf project deploy start, query the org with sf data query when state inspection is needed.
  5. Surface decisions back to the user — when a step requires a choice that materially affects scope or risk, ask using the platform's blocking question tool rather than guessing.

Read the full file on GitHub · 42 lines

Changes

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.

  1. 8d ago First seen · 42 lines · 74 tokens per session scan A e5178edd8109

Subscribe to this mod's changes

sf-ideate is a skill published in the GitHub repository divingsbysangam/salesforce-compound-engineering-plugin (10 stars, last pushed 3d ago), licensed MIT. It adds 74 tokens to every session and 630 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-31.

Planning
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 103 tokens

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…

microsoft/vscode · 72 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens