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 fsl-inventory-managementgit 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/fsl-inventory-management)<a href="https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/fsl-inventory-management"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/fsl-inventory-management/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/fsl-inventory-management"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/fsl-inventory-management.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.00079 | $0.03819 |
| Opus 5 | $0.00039 | $0.01910 |
| Sonnet 5 | $0.00016 | $0.00764 |
| Haiku 4.5 | $0.00008 | $0.00382 |
Grade A, and why
fsl-inventory-management 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FSL Inventory Management
This skill activates when a practitioner needs to configure or troubleshoot the Field Service Lightning inventory object model — covering stock locations, stock movement, parts consumption on work orders, replenishment ordering, and the auto-generated audit trail. It does NOT cover CPQ product catalog configuration, OCI (Omnichannel Inventory) for B2B Commerce, or ERP warehouse integration patterns.
Before Starting
Gather this context before working on anything in this domain:
- Confirm the Field Service managed package is installed and Field Service is enabled under Setup > Field Service Settings. The inventory objects (ProductItem, ProductTransfer, ProductRequest, ProductConsumed, ProductItemTransaction) are part of the FSL data model and do not exist without the package.
- Identify all Location record types in use: fixed warehouses, depots, and technician vans. Van locations must have the Mobile Location checkbox enabled or field technicians cannot see their own stock in the FSL mobile app.
- Confirm whether ProductItemTransaction records are being managed manually anywhere — they are auto-generated by the platform and must never be directly created or deleted. Manual DML on these records corrupts QuantityOnHand on the linked ProductItem.
- Understand the replenishment trigger: is it manual (dispatcher creates ProductRequest), threshold-based (custom automation), or driven by work order completion events?
Core Concepts
The Six Core Inventory Objects
The FSL inventory data model has six primary objects. Each has a distinct role and must not be confused with the others.
ProductItem — represents a quantity of a specific Product2 stored at a specific Location. QuantityOnHand is the live count. This is the master stock record. Do not manually update QuantityOnHand — it is maintained by the platform as ProductTransfer and ProductConsumed records are created and updated.
ProductTransfer — records the movement of stock from one Location to another (e.g., warehouse → technician van). QuantityOnHand on the source ProductItem does NOT decrease when the transfer is created. It decreases only when the transfer status is set to Received. This is the single most common source of incorrect inventory counts.
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 · 232 lines · 79 tokens per session scan A aebee588b36d
fsl-inventory-management is a skill published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (3 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 79 tokens to every session and 3,819 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
supply-chain-expert
Build comprehensive supply chain solutions including demand planning, inventory management, supplier coordination, and logistics optimization. Use when the user mentions supply chain, demand planning or forecasting, inventory and safety stock, procurement, supplier management, warehousing, or logistics optimization.
setup-platform-development
Help set up the platform development policy — contribution mode, governance, and sharing.
inventory-gap-audit
Audit the product inventory for missing metadata, version records, and lifecycle gaps.
version-discovery
Discover which products are missing version numbers and surface what version data exists.
advance-product
Help advance a product to the next lifecycle stage after checking stage-gate criteria.
lifecycle-review
Review products by lifecycle stage and identify which need attention.