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 Avinava/sf-documentation-knowledge --skill salesforce-app-limits-cheatsheetgit clone --depth 1 https://github.com/Avinava/sf-documentation-knowledgeWrote 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/avinava/sf-documentation-knowledge/salesforce-app-limits-cheatsheet)<a href="https://agentmods.dev/skills/avinava/sf-documentation-knowledge/salesforce-app-limits-cheatsheet"><img src="https://agentmods.dev/badge/skills/avinava/sf-documentation-knowledge/salesforce-app-limits-cheatsheet.svg" alt="Measured on agentmods" 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.00027 | $0.00227 |
| Opus 5 | $0.00014 | $0.00113 |
| Sonnet 5 | $0.00005 | $0.00045 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
sf-knowledge-salesforce-app-limits-cheatsheet 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 3d 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
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 3d ago First seen · 21 lines · 27 tokens per session scan A 04a8396ad7c4
sf-knowledge-salesforce-app-limits-cheatsheet is a skill published in the GitHub repository Avinava/sf-documentation-knowledge (1 stars, last pushed 1mo ago), with no licence file. It adds 27 tokens to every session and 227 once invoked, about $0.0001 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
nebula-logger-instrumentation
Use this skill when the user wants to add or update Nebula Logger instrumentation in Apex, LWC, Aura, Flow, or OmniStudio. Covers logging APIs, save patterns, record association, scenarios, tags, async transaction linking, and save method selection.
mem0-status
Diagnoses mem0 connectivity, API key validity, and memory read/write functionality. Use when memory operations fail, searches return empty, addmemory errors occur, or to verify the plugin is working correctly.
data-fetching
Use when implementing or debugging ANY network request, API call, or data fetching. Covers fetch API, axios, React Query, SWR, error handling, caching strategies, offline support.
nebula-logger-best-practices
Use this skill when the user wants to review, harden, or standardize Nebula Logger usage across a Salesforce team. Covers operational logging standards, environment-aware settings, limit-aware design, and governance guardrails.
nebula-logger-console
Use this skill when the user wants to browse, filter, or investigate Nebula Logger data in the Salesforce UI. Covers the Logger Console app, list views on Logc / LogEntryc / LogEntryTagc / LoggerScenarioc / LoggerTagc, related-list navigation, the Log record page and its LWCs, and how admins and support engineers use…
rest-graphql-debug
Debug REST/GraphQL APIs: status codes, auth, schemas, repro.