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-pricing-diagnosticsgit 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-pricing-diagnostics)<a href="https://agentmods.dev/skills/arohitu/salesforce-revenue-cloud-skills/revenue-cloud-pricing-diagnostics"><img src="https://agentmods.dev/badge/skills/arohitu/salesforce-revenue-cloud-skills/revenue-cloud-pricing-diagnostics/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-pricing-diagnostics"><img src="https://agentmods.dev/badge/skills/arohitu/salesforce-revenue-cloud-skills/revenue-cloud-pricing-diagnostics.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00112 | $0.01552 |
| Opus 5 | $0.00056 | $0.00776 |
| Sonnet 5 | $0.00022 | $0.00310 |
| Haiku 4.5 | $0.00011 | $0.00155 |
Grade A, and why
revenue-cloud-pricing-diagnostics 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 12d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Revenue Cloud Pricing Diagnostics
Use this skill to analyze Salesforce Revenue Cloud pricing implementations on core Salesforce Revenue Cloud / Agentforce Revenue Management. This is not Salesforce CPQ / Steelbrick CPQ. Do not start from SBQQ__* objects, CPQ price rules, product rules, or quote calculator plugins unless the user is explicitly asking about Salesforce CPQ instead of Revenue Cloud.
Default Workflow
When the user asks how a pricing field is populated, why a price changed, or how pricing logic works:
- Identify the commercial object and field: Quote, Quote Line, Order, Order Item, Contract, Asset, or another mapped object. In an SFDX project, fields are usually under
force-app/main/default/objects/<ObjectApiName>/fields/<FieldApiName>.field-meta.xml. Inspect XML tags such as<fullName>,<type>,<formula>,<formulaTreatBlanksAs>,<precision>,<scale>, and<required>. - Read the field metadata. Determine whether it is stored, formula, standard, custom, read-only, or calculated elsewhere. If the field is a formula, trace the fields referenced in
<formula>before assuming pricing writes to it directly. - Find matching context attributes and context tags in context definitions. In SFDX source, these are usually under
force-app/main/default/contextDefinitions/*.contextDefinition-meta.xml. Inspect<contextNodes>,<contextAttributes>,<title>,<dataType>,<fieldType>,<transient>, and<contextTags><title>.... - Inspect context mappings for both hydration and persistence in the same context definition metadata. Look under
<contextMappings>,<contextMappingIntents><mappingIntent>,<contextNodeMappings>,<contextAttributeMappings>,<contextAttrHydrationDetails>,<objectName>,<queryAttribute>,<contextAttribute>,<contextInputAttributeName>,<contextNode>, and<object>. - Trace bidirectionally between sObject fields and pricing tags. If a pricing step writes to a tag such as
EffectiveFromorEffectiveTo, find the context attribute that owns that tag, confirm it isinputoutputor output-capable, then trace its persistence mapping back to the target sObject field. Do not conclude a field is read-only to pricing until the save/writeback mapping has been checked. - Search expression set versions for the context tag, variable, output parameter, assignment, formula, aggregation, list operation, matrix lookup, or stop-pricing step. In SFDX source, pricing procedures are usually under
force-app/main/default/expressionSetVersion/*.expressionSetVersion-meta.xml. Inspect<variables>,<name>,<input>,<output>,<dataType>,<steps>,<actionType>,<customElement>,<parameters>,<sequenceNumber>,<parentStep>, and<stepType>. - Inspect pricing elements and decision table references. Decision tables are usually under
force-app/main/default/decisionTables/*.decisionTable-meta.xml, with dataset links underforce-app/main/default/decisionTableDatasetLinks/*.decisionTableDatasetLink-meta.xml. Confirm<decisionTableParameters>,<fieldName>,<usage>,<operator>,<sequence>,<isRequired>, condition criteria, outputs, backing object/source, and active status. - Identify procedure-plan sequence when available. Procedure-plan deployable metadata may not exist in source; if absent, query the org for
ProcedurePlanDefinition,ProcedurePlanDefinitionVersion,ProcedurePlanSection, andProcedurePlanOption. Apex hooks referenced by procedure plans are usually underforce-app/main/default/classes/<ClassName>.cls. - Produce a lineage report with evidence, likely failure points, and focused next checks.
What ships with it
6 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.
- 12d ago First seen · 76 lines · 112 tokens per session scan A f0874eda62c4
revenue-cloud-pricing-diagnostics is a skill published in the GitHub repository arohitu/salesforce-revenue-cloud-skills (18 stars, last pushed 11d ago), licensed MIT. It adds 112 tokens to every session and 1,552 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-08-30.
Other skills, from other repositories
b2c-logs
Retrieve and search logs from B2C Commerce instances using the b2c CLI. Use this skill whenever the user needs to view server logs, search for errors, filter log entries by level or time, or monitor logs in real-time. Also use when the user reports a 500 error, broken checkout, failing job, or any server-side issue…
revenuecat-troubleshoot
Diagnose and resolve RevenueCat integration issues — inspects dashboard configuration through the RevenueCat MCP, walks the SDK debug logs, and covers code-side gotchas. Use when the user says offerings are empty, products not loading, entitlement not active after purchase, paywall won't load, transactions not…
doctor
Audits an existing PagoKit integration in the current project against the generated per-provider checklist, so it covers every provider in the catalog rather than a hardcoded few. Checks .gitignore covers .env, that env vars are present and use test-key prefixes, that the webhook secret looks valid, that the webhook…
wcs-health-check-processing
WooCommerce Subscriptions 8.8+ Health Check and Processing Reliability playbook for missing renewal schedules, automatic-renewal candidates, guarded Resolve actions, dedicated Action Scheduler processing, web cron, health-check tables, logs, AJAX nonces, and queue filters. Use for WCS Health Check…
sealeap-amazon-featured-offer-loss-triage
Triage loss of the Amazon Featured Offer by checking account health, order defect signals, price competitiveness, offer and fulfillment state, listing classification, unauthorized sellers, and external price evidence before escalating. Use when the Buy Box or purchase button disappears or repeatedly returns. Do not…
wc-logging
Add production-safe WooCommerce logs with wcgetlogger(). Covers stable sources, severity levels and thresholds, structured JSON context, correlation IDs, sensitive-data redaction, WooCommerce 11.0 file-v2 formatting and batched retention cleanup, volume control, custom handlers, and why logs are not durable business…