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 PranavNagrecha/AwesomeSalesforceSkills --skill compliance-documentation-requirementsgit clone --depth 1 https://github.com/PranavNagrecha/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/pranavnagrecha/awesomesalesforceskills/compliance-documentation-requirements)<a href="https://agentmods.dev/skills/pranavnagrecha/awesomesalesforceskills/compliance-documentation-requirements"><img src="https://agentmods.dev/badge/skills/pranavnagrecha/awesomesalesforceskills/compliance-documentation-requirements/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/pranavnagrecha/awesomesalesforceskills/compliance-documentation-requirements"><img src="https://agentmods.dev/badge/skills/pranavnagrecha/awesomesalesforceskills/compliance-documentation-requirements.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.00148 | $0.04514 |
| Opus 5 | $0.00074 | $0.02257 |
| Sonnet 5 | $0.00030 | $0.00903 |
| Haiku 4.5 | $0.00015 | $0.00451 |
Grade A, and why
compliance-documentation-requirements 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 8d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 8d ago First seen · 231 lines · 148 tokens per session scan A 8d7a780e476e
compliance-documentation-requirements is a skill published in the GitHub repository PranavNagrecha/AwesomeSalesforceSkills (17 stars, last pushed 9d ago), with no licence file. It adds 148 tokens to every session and 4,514 once invoked, about $0.0007 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-04.
Other skills, from other repositories
compliance-documentation-requirements
Use when setting up or auditing how compliance documentation is structured, collected, and preserved for regulatory audit in Salesforce FSC — covering KYC data collection workflows, AML screening integration setup, audit trail configuration, and regulatory reporting readiness. Triggers: KYC form setup, AML integration…
regtech-expert
Expert in regulatory technology, compliance automation, KYC/AML, transaction monitoring, risk assessment, and automated reporting. Use when the user mentions compliance, KYC, AML, transaction monitoring, risk assessment, or regulatory reporting, or when the task involves KYC/AML Compliance, KYC/AML Program, Regulatory…
onboarding
Full KYC customer onboarding with mandatory Step 0 independent verification (5+1 searches), 17 sequential stagegates requiring explicit analyst consent, deterministic four-factor risk scoring, case folder auto-creation, 4-sheet Excel dashboard, 17-section PDF report, and immutable audit trail. Covers UK/EU (AMLD5), US…
risk-assessment
Deterministic heuristic risk scoring using a four-factor weighted model (Geographic 30%, Customer 35%, Product 25%, Channel 10%) aligned with Basel III, EBA Guidelines, FATF standards, and FinCEN guidance. Bands: LOW (0-20), MEDIUM (21-60), HIGH (61-80), CRITICAL (81-100).
screening
Comprehensive sanctions and PEP screening against 12+ databases (OFAC, EU, UK, UN, INTERPOL) with false positive assessment, HITL decision gates, and regulatory-compliant documentation.
refresh
Periodic customer refresh with re-verification of original due diligence to detect material changes and maintain compliance with ongoing due diligence requirements. Triggers include time-based review (annual HIGH risk, 2-3 year intervals for MEDIUM/LOW), risk-based escalation (score changes, business pivots), and…