agentmods.dev

audit-validation-rules

audit-validation-rules is a command for Claude Code from BanibrataChatterjee/AwesomeSalesforceSkills. It costs 0 tokens per session (358 once invoked), scanned A, a copy of audit-reports, Apache-2.0.

A legacy command for auditing Salesforce validation rules, which prevent records from being saved when conditions are not met. It now forwards requests to the broader audit router.

In plain words
What is it for?
Use it when reviewing a validation rule for bypass behaviour, record-type relevance, conflicts with Flows, and message quality. New usage should use the canonical audit-router command.
Why use it?
It preserves the older command while centralising auditing in one router. This reduces duplicated audit entry points while retaining checks specific to validation rules.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md).

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is [`audit-router`](../agents/audit-router/AGENT.md) with.

not rated 4repo 6mo ago A scan 0 tokens copy · 80% Apache-2.0

Good fit Use it when reviewing a validation rule for bypass behaviour, record-type relevance, conflicts with Flows, and message quality. New usage should use the canonical audit-router command.

Compare 6 commands from other repositories ↓
View source ↗ BanibrataChatterjee/AwesomeSalesforceSkills
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/BanibrataChatterjee/AwesomeSalesforceSkills
agentmods
npx agentmods add commands/banibratachatterjee/awesomesalesforceskills/audit-validation-rules

Made for: Claude Code.

Wrote 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.

agentmods badge for audit-validation-rules

README.md
[![agentmods](https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/audit-validation-rules/github.svg)](https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/audit-validation-rules)
Your own site
<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/audit-validation-rules"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/audit-validation-rules/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.

agentmods 80×15 button for audit-validation-rules

Your own site · 80×15
<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/audit-validation-rules"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/audit-validation-rules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 358 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 80% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00358
Opus 5.5 $0.00000 $0.00143
Sonnet 5.5 $0.00000 $0.00072
Haiku 4.5 $0.00000 $0.00036

Measured 2mo ago against content hash 65afbee7c91f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

audit-validation-rules 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 2mo 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.

Origin

This is a copy

80% identical to audit-reports — 19 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

commands/audit-validation-rules.md · 39 lines

What it actually says

/audit-validation-rules — LEGACY ALIAS (Wave 3b-1)

Deprecation notice: this command is now an alias. It invokes the audit-router with --domain=validation_rule and emits this deprecation notice. Switch to the canonical /audit-router form at your convenience; the alias ships until the removal window declared in docs/MIGRATION.md (Wave 7).

Canonical form

/audit-router --domain validation_rule --object <ApiName> --target-org <alias>

Alias behavior

Running /audit-validation-rules <args> is equivalent to:

/audit-router --domain validation_rule <args>

The VR-specific rule table (bypass contract, Wrong-Tool classification, record-type relevance gate, VR ↔ flow conflicts, message quality) is preserved verbatim in classifiers/validation_rule.md.

Why the change

Wave 3b-1 of the redesign consolidated 5 auditors into one router. See agents/_shared/harnesses/audit_harness/README.md for the rationale.

See also

Changes

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.

  1. 2mo ago First seen · 39 lines · 0 tokens per session scan A 65afbee7c91f

Subscribe to this mod's changes

audit-validation-rules is a command published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (4 stars, last pushed 6mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 358 tokens. A static security scan graded it A with 0 findings. It is 80% identical to audit-reports, differing in 19 lines, and is treated as a copy.

Related

audit-validation-rules compared with commands from other repositories

audit-validation-rules next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
audit-validation-rulesBanibrataChatterjee/AwesomeSalesforceSkillsCommand46mo agoApache-2.0A0Claude Code
checklistgithub/spec-kitCommand148ktodayMITA13Claude Code
clarifygithub/spec-kitCommand148ktodayMITA27Claude Code
specifygithub/spec-kitCommand148ktodayMITA13Claude Code
analyzegithub/spec-kitCommand148ktodayMITA26Claude Code
convergegithub/spec-kitCommand148ktodayMITA35Claude Code
implementgithub/spec-kitCommand148ktodayMITA14Claude Code