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 agentmods add skills/avinava/sf-documentation-knowledge/api-analyticsnpx skills add Avinava/sf-documentation-knowledge --skill api-analyticsgit clone --depth 1 https://github.com/Avinava/sf-documentation-knowledgeWhat 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 | $0.00023 | $0.00213 |
| Opus 5 | $0.00012 | $0.00106 |
| Sonnet 5 | $0.00005 | $0.00043 |
| Haiku 4.5 | $0.00002 | $0.00021 |
Grade A, and why
sf-knowledge-api-analytics 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 yesterday.
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.
- yesterday First seen · 21 lines · 23 tokens per session scan A 8a27c83268e3
sf-knowledge-api-analytics is a skill published in the GitHub repository Avinava/sf-documentation-knowledge (1 stars, last pushed 1mo ago), with no licence file. It adds 23 tokens to every session and 213 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-08-31.
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.
nebula-logger-plugin-development
Use this skill when the user wants to build a new plugin that extends Nebula Logger - for example, custom trigger handlers on LogEntryEvente / Logc / LogEntryc, custom purge actions, or Slack-style outbound integrations. Covers the plugin framework interfaces, LoggerPluginmdt configuration, package layout, and testing…
nebula-logger-testing-your-code
Use this skill when the user wants to write Apex or LWC tests for code that calls Nebula Logger. Covers observing that the right entries were buffered, controlling logging levels inside tests, isolating tests from persisted Logc / LogEntryc / LogEntryTagc / LoggerScenarioc / LoggerTagc records, and Nebula Logger APIs…
nebula-logger-purging-and-retention
Use this skill when the user wants to configure how long Nebula Logger keeps log records before deleting or archiving them. Covers retention date semantics on Logc, the LogBatchPurger batch job, LogBatchPurgeScheduler, purge action values, and how to tune retention per user, profile, or scenario.
nebula-logger-install
Use this skill when the user wants to install and configure Nebula Logger in a Salesforce org for the first time. Covers package selection, installation paths, permissions, LoggerSettingsc hierarchy, and first-run troubleshooting.
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.