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 jongpie/NebulaLogger --skill nebula-logger-purging-and-retentiongit clone --depth 1 https://github.com/jongpie/NebulaLoggerWrote 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/jongpie/nebulalogger/nebula-logger-purging-and-retention)<a href="https://agentmods.dev/skills/jongpie/nebulalogger/nebula-logger-purging-and-retention"><img src="https://agentmods.dev/badge/skills/jongpie/nebulalogger/nebula-logger-purging-and-retention/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/jongpie/nebulalogger/nebula-logger-purging-and-retention"><img src="https://agentmods.dev/badge/skills/jongpie/nebulalogger/nebula-logger-purging-and-retention.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 21 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00079 | $0.01439 |
| Opus 5 | $0.00039 | $0.00720 |
| Sonnet 5 | $0.00016 | $0.00288 |
| Haiku 4.5 | $0.00008 | $0.00144 |
Grade A, and why
nebula-logger-purging-and-retention 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 12d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Log Retention and Purging in Nebula Logger
The Retention Model
Every Log__c record has a LogRetentionDate__c. When that date passes, the log becomes eligible for purging by LogBatchPurger. The retention date is set at insert time on Log__c from a combination of:
LoggerSettings__c.DefaultNumberOfDaysToRetainLogs__con the effective hierarchy record.- Optionally,
LoggerScenarioRule__mdt.NumberOfDaysToRetainLogs__cwhen the log's scenario matches a scenario rule (scenario-specific overrides win over the hierarchy default).
If no retention days are configured, LogRetentionDate__c is left null and the log is never auto-purged.
LoggerSettings__c Retention Fields
The retention side of LoggerSettings__c is a hierarchy custom setting - values cascade org default -> profile -> user. The relevant fields:
| Field | Purpose |
|---|---|
DefaultNumberOfDaysToRetainLogs__c |
Days between log insert and eligibility for purging. Null = no automatic purge. |
DefaultLogPurgeAction__c |
What the batch job does when it processes an eligible log. Default value is Delete. |
IsEnabled__c |
Master switch; disabling logging at a hierarchy level also stops new Log__c records from being written for those users. |
Purge Actions
Log__c.LogPurgeAction__c (populated from LoggerSettings__c.DefaultLogPurgeAction__c at insert time) tells LogBatchPurger what to do when a log ages out:
Delete(default): The batch job hard-deletes theLog__cand its childLogEntry__crecords. They do not sit in the Recycle Bin.- Plugin-provided actions: Some Nebula Logger plugins add their own purge actions. For example, the
big-object-archivingplugin copies logs into a big object before deletion so the data remains queryable long-term. When such a plugin is installed, its purge action becomes a valid value forLogPurgeAction__c.
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.
- 12d ago First seen · 88 lines · 79 tokens per session scan A e2bff79cc522
nebula-logger-purging-and-retention is a skill published in the GitHub repository jongpie/NebulaLogger (960 stars, last pushed today), licensed MIT. It adds 79 tokens to every session and 1,439 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-08-30.
Other skills, from other repositories
sfcc-caching
Unified caching playbook for SFCC (page cache vs custom cache vs service response cache). Use this when improving performance, reducing external calls, designing cache keys/TTLs, or debugging stale cache behavior.
sf-knowledge-bi-dev-guide-sql
Apply Salesforce knowledge and best practices for SQL for Analytics Developer Guide.
sf-knowledge-bigobjects
Apply Salesforce knowledge and best practices for Big Objects Implementation Guide.
sf-knowledge-field-history-retention
Apply Salesforce knowledge and best practices for Field Audit Trail Implementation Guide.
sf-knowledge-sfFieldRef
Apply Salesforce knowledge and best practices for Salesforce Field Reference Guide.
sf-knowledge-soql-sosl
Apply Salesforce knowledge and best practices for SOQL and SOSL Reference.