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 formula-fieldsgit 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/formula-fields)<a href="https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/formula-fields"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/formula-fields/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/formula-fields"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/formula-fields.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.00071 | $0.01594 |
| Opus 5 | $0.00036 | $0.00797 |
| Sonnet 5 | $0.00014 | $0.00319 |
| Haiku 4.5 | $0.00007 | $0.00159 |
Grade A, and why
formula-fields 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Salesforce Admin expert in formula field design. Your goal is to create formulas that stay readable, perform acceptably at scale, and return correct values across blank data, cross-object references, and reporting use cases.
Before Starting
Check for salesforce-context.md in the project root. If present, read it first.
Only ask for information not already covered there.
Gather if not available:
- What should the formula return: text, number, currency, percent, checkbox, date, or URL/image?
- Is the value for display only, or does the business actually need a stored snapshot?
- How many parent relationships does the formula traverse?
- Will this formula be used in reports, list views, automation, or integrations?
- What null or blank states must be handled explicitly?
How This Skill Works
Mode 1: Build from Scratch
Use this for a new formula requirement.
- Confirm a formula field is the right tool; if the value must be historically preserved, it should be stored, not recalculated.
- Choose the return type first and keep the formula aligned to that type.
- Write the simplest readable expression that solves the requirement.
- Handle blanks explicitly for every referenced field that can be empty.
- Keep cross-object references shallow and test the formula in reports and list views, not just on record detail.
Mode 2: Review Existing
Use this for inherited formulas or orgs with unreadable formula sprawl.
- Check whether the formula should be a real field populated by Flow instead.
- Check nesting depth, repeated logic, and whether
CASE()or helper formulas would simplify it. - Check for cross-object traversal, heavy use in reports, and other performance smells.
- Check null handling by field type, not by guesswork.
- Check field descriptions so the next admin can understand the business rule without reverse engineering it.
Mode 3: Troubleshoot
Use this when a formula returns the wrong value, behaves inconsistently, or causes reporting pain.
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 · 134 lines · 71 tokens per session scan A 4b75494fb9e3
formula-fields is a skill published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (3 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 71 tokens to every session and 1,594 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
hotpath_bump
Bump the hotpath version number across the workspace and related files. Updates crate versions in Cargo.toml files (exact patch version) and version references in the backend middleware, hotpathinit skill, and README (major.minor only). Use when the user wants to bump, bump the version, or release a new hotpath…
hunt-django
Hunt Django-specific vulnerabilities: DRF permission gaps, ORM injection, and admin exploitation.
owl-admin-app-dev
Use this skill when developing an application that installed slowlyo/owl-admin, especially backend CRUD, menus, permissions, controllers, services, routes, config/admin.php, app/Admin, helper functions, settings(), adminpages(), AdminPipeline, upload/file preview issues, route conflicts, custom login/menu examples, or…
owl-admin-devtools-generator
A development guide for Owl Admin, a Laravel-based administration system, covering its code generator, API templates, relationships, and visual pages.
owl-admin-ops-commands
Use this skill for Owl Admin installation, publishing assets, upgrades, diagnostics, database inspection, menu maintenance, user creation, password reset, route generation, IDE helper, admin:publish, admin:install, admin:update, admin:doctor, admin:db, admin:menu, admin:create-user, or deployment troubleshooting.
owl-admin-extension-module
A development guide for Owl Admin extensions and modules. An extension adds optional functionality, while a module groups related routes, settings, menus, and permissions.