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 BanibrataChatterjee/AwesomeSalesforceSkills --skill industries-energy-utilities-setupgit clone --depth 1 https://github.com/BanibrataChatterjee/AwesomeSalesforceSkillsWrote 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/banibratachatterjee/awesomesalesforceskills/industries-energy-utilities-setup)<a href="https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/industries-energy-utilities-setup"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/industries-energy-utilities-setup/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/banibratachatterjee/awesomesalesforceskills/industries-energy-utilities-setup"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/industries-energy-utilities-setup.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.00088 | $0.03351 |
| Opus 5 | $0.00044 | $0.01675 |
| Sonnet 5 | $0.00018 | $0.00670 |
| Haiku 4.5 | $0.00009 | $0.00335 |
Grade A, and why
industries-energy-utilities-setup 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 9d 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Industries Energy Utilities Setup
This skill activates when a practitioner needs to configure the operational foundation of Salesforce Energy and Utilities (E&U) Cloud: enabling the license, assigning permission sets, setting up industry-specific objects (ServicePoint, Meter, MeterReading, Consumption, ServiceAccount, ServiceContract, RatePlan), connecting the external Customer Information System (CIS) or billing platform, and configuring service order management workflows. It does not cover schema reference queries or data model architecture — use architect/industries-data-model for that.
Before Starting
Gather this context before working on anything in this domain:
- Confirm that the Energy and Utilities Cloud license is provisioned in the org — Setup > Installed Packages must show the E&U managed package. All industry-specific objects (ServicePoint, Meter, RatePlan, ServiceContract) are unavailable without this license.
- Identify the market type: regulated utility markets and competitive/deregulated markets have different service point configuration rules, rate plan assignment logic, and integration requirements. Applying regulated-market setup steps in a competitive-market org (or vice versa) produces silently incorrect billing data.
- The most common wrong assumption is that standard Salesforce admin setup patterns (user provisioning, record types, page layouts) transfer directly to E&U Cloud without modification. E&U Cloud requires specific permission sets from the managed package and industry-specific object hierarchies that do not map 1:1 to standard Account/Asset/Contract objects.
Core Concepts
Industry-Specific Object Hierarchy
Energy and Utilities Cloud adds a set of standard objects on top of core Salesforce Account and Asset objects. These objects require the E&U Cloud license and are not available in standard Salesforce editions:
- ServicePoint — the physical metering location where energy or utility service is delivered or measured. A ServicePoint has a geographic address, a service type (electricity, gas, water), and a market segment. It is distinct from Account (the customer) and from Asset (equipment). One Account may have multiple ServicePoints (e.g., a commercial customer with multiple meters across a campus).
- Meter — the physical or virtual metering device installed at a ServicePoint. A ServicePoint can have one or more Meters over its lifetime (meter replacements are modeled as new Meter records linked to the same ServicePoint).
- MeterReading — an individual usage reading taken from a Meter at a point in time. MeterReadings are the raw inputs used to calculate consumption.
- Consumption — a calculated usage record derived from one or more MeterReadings over a billing period. Consumption records are what rate plans operate against to generate charges.
- ServiceAccount — in E&U Cloud, this is an Account record with the Service Account record type representing a utility account associated with one or more ServicePoints. It is distinct from a commercial or residential billing account.
- ServiceContract — the legal agreement between the utility provider and the customer for service at one or more ServicePoints. It carries the effective dates, service type, and links to the applicable RatePlan.
- RatePlan — the tariff or pricing structure that determines how charges are calculated from Consumption records. RatePlan assignment is not standalone — it depends on service type, market segment (regulated or competitive), and the external CIS or billing system integration.
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.
- 9d ago First seen · 209 lines · 88 tokens per session scan A 3ebdb4b22e48
industries-energy-utilities-setup is a skill published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (3 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 88 tokens to every session and 3,351 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-09-03.
Other skills, from other repositories
antd
Use when the user's task involves Ant Design (antd) — writing antd components, debugging antd issues, querying antd APIs/props/tokens/demos, migrating between antd versions, or analyzing antd usage in a project. Triggers on antd-related code, imports from 'antd', or explicit antd questions.
v3-create-crud
A page generator for standard create, read, update, and delete screens, commonly called CRUD screens. It uses Element Plus, a Vue user-interface library, to build tables, searches, pagination, forms, and delete confirmations.
hunt-django
Hunt Django-specific vulnerabilities: DRF permission gaps, ORM injection, and admin exploitation.
v3-upsert-route
A route configuration helper for projects that keep their routes in `src/router/index.ts`. It creates or updates permanent and permission-controlled pages, including titles, icons, and child routes.
v3-use-composables
Documentation for reusable Vue functions in a project, covering device detection, asynchronous dropdown data, loading screens, pagination, routing, themes, page titles, and watermarks.
pro-upgrade
An upgrade guide for projects built with Ant Design Pro, a React-based application template for business software. It compares the project with the latest official template and merges framework updates while preserving application code.