Borrowing it
Nothing to install: this file belongs to deejay-hub/salesforce-ada-agent-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/deejay-hub/salesforce-ada-agent-skills/main/.claude/skills/decide/SKILL.mdgit clone --depth 1 https://github.com/deejay-hub/salesforce-ada-agent-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/skills/deejay-hub/salesforce-ada-agent-skills/decide)<a href="https://agentmods.dev/skills/deejay-hub/salesforce-ada-agent-skills/decide"><img src="https://agentmods.dev/badge/skills/deejay-hub/salesforce-ada-agent-skills/decide/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/deejay-hub/salesforce-ada-agent-skills/decide"><img src="https://agentmods.dev/badge/skills/deejay-hub/salesforce-ada-agent-skills/decide.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.00042 | $0.01646 |
| Opus 5 | $0.00021 | $0.00823 |
| Sonnet 5 | $0.00008 | $0.00329 |
| Haiku 4.5 | $0.00004 | $0.00165 |
Grade A, and why
decide 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 10d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are in DECIDE mode. Guide the user through a structured decision pipeline for "$ARGUMENTS".
Pipeline
Execute these steps IN ORDER. Pause for user input between each step. Do not skip steps.
Step 1: Discovery
Gather context using AskUserQuestion. Ask about:
- Business problem or technical challenge
- Key numbers (record volumes, user count, transaction frequency)
- Salesforce products, editions, and existing customizations
- Delivery timeline
- Budget, compliance, or technical constraints
Skip questions already answered in "$ARGUMENTS". Do NOT search documentation during discovery.
Limit discovery to 2 rounds of questions (max 8 questions total). If critical context is still missing after Step 1, gather it in Step 4's differentiating questions instead.
Step 2: Solution Options
2a. Research
Search official Salesforce documentation using your available MCP tools. Focus on relevant approaches, architecture patterns, and platform capabilities. Restrict searches to official reference documentation only (developer.salesforce.com, help.salesforce.com, architect.salesforce.com) — never blogs or videos.
Multiple search calls are allowed in this step. Use as many as needed to adequately research the option space.
2b. Propose Options
Propose 3-4 options based on research results.
Read knowledge/formats/options-format.md for the exact output format. Follow it precisely.
2c. Validate Options
Before presenting options to the user, validate EVERY proposed option against official documentation:
- For each option, search official documentation with a targeted query to confirm the option is a documented, supported capability (e.g., product compatibility, supported deployment targets, feature availability).
- Fetch full page content when a snippet is insufficient to confirm support.
- For each option, record a validation status:
- Confirmed — Documentation explicitly supports this option's technical approach
- Unconfirmed — Documentation does not explicitly address this combination; requires vendor confirmation before committing
- Drop any option that documentation explicitly contradicts (e.g., a product combination documented as unsupported). Explain why it was removed.
- Present the options table with a "Docs" column showing the validation status and a citation.
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.
- 10d ago First seen · 138 lines · 42 tokens per session scan A 5eac04efe030
decide is a skill published in the GitHub repository deejay-hub/salesforce-ada-agent-skills (9 stars, last pushed 3mo ago), licensed MIT. It adds 42 tokens to every session and 1,646 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 skills, from other repositories
claude-md-improver
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…
agent-platform-rag-engine-management
Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
google-cloud-solution-agentic-analytics-spark-knowledge-catalog
Discovers requirements and generates guidance to design and deploy a governed, secure agentic-analytics solution for data that's distributed across Google Cloud, other cloud providers, or on-premises. Data that's outside Google Cloud (such as data from Databricks, Snowflake, Salesforce, SAP, or Oracle systems) is…