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 arohitu/salesforce-revenue-cloud-skills --skill revenue-cloud-decision-tablegit clone --depth 1 https://github.com/arohitu/salesforce-revenue-cloud-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/arohitu/salesforce-revenue-cloud-skills/revenue-cloud-decision-table)<a href="https://agentmods.dev/skills/arohitu/salesforce-revenue-cloud-skills/revenue-cloud-decision-table"><img src="https://agentmods.dev/badge/skills/arohitu/salesforce-revenue-cloud-skills/revenue-cloud-decision-table/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/arohitu/salesforce-revenue-cloud-skills/revenue-cloud-decision-table"><img src="https://agentmods.dev/badge/skills/arohitu/salesforce-revenue-cloud-skills/revenue-cloud-decision-table.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 25 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 35 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00065 | $0.01777 |
| Opus 5 | $0.00032 | $0.00889 |
| Sonnet 5 | $0.00013 | $0.00355 |
| Haiku 4.5 | $0.00006 | $0.00178 |
Grade A, and why
revenue-cloud-decision-table 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 13d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Revenue Cloud Decision Table
Use this skill to find a Salesforce Revenue Cloud Decision Table, determine the inputs needed to invoke it, collect missing runtime values, and verify what the table returns from the org.
Default Workflow
- Identify the target org alias or username. If missing, ask for it or use the Salesforce CLI default org only after saying so.
- Find the Decision Table Id from the user's table name, developer name, label, pricing component, or business scenario.
- Inspect the table metadata and parameters to identify input fields, output fields, operators, and whether a dataset link name is required.
- Build a
conditionspayload. If runtime values are missing, ask the user for only the missing input values; otherwise infer them from provided quote/order/product/pricing context. - Invoke the table through the Connect REST API and report the returned
outcomeList[].values,outcomeType,successStatus, and any errors. - Compare the outcome with the user's expected pricing behavior and call out mismatched inputs, wrong dataset link, inactive table, stale refresh status, or auth problems.
Helper Scripts
The scripts require Salesforce CLI sf, jq, and an authenticated target org.
scripts/find-decision-table.sh: finds candidate Decision Tables by search text or developer name.scripts/inspect-decision-table-inputs.sh: queriesDecisionTableParametermetadata and emits a payload skeleton withnullvalues for inputs the agent must fill.scripts/invoke-decision-table.sh: usessf org displayto get the org instance URL and access token, then posts a payload to the Decision Table invocation endpoint.
Run scripts from this skill folder or pass their full path:
.cursor/skills/revenue-cloud-decision-table/scripts/find-decision-table.sh --target-org <alias> --search "Volume"
.cursor/skills/revenue-cloud-decision-table/scripts/inspect-decision-table-inputs.sh --target-org <alias> --decision-table-id 0lD...
.cursor/skills/revenue-cloud-decision-table/scripts/invoke-decision-table.sh --target-org <alias> --decision-table-id 0lD... --payload-file payload.json
What ships with it
3 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.
- 13d ago First seen · 189 lines · 65 tokens per session scan A 114e070ad2b1
revenue-cloud-decision-table is a skill published in the GitHub repository arohitu/salesforce-revenue-cloud-skills (18 stars, last pushed 11d ago), licensed MIT. It adds 65 tokens to every session and 1,777 once invoked, about $0.0003 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-30.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…