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-plugin-developmentgit 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-plugin-development)<a href="https://agentmods.dev/skills/jongpie/nebulalogger/nebula-logger-plugin-development"><img src="https://agentmods.dev/badge/skills/jongpie/nebulalogger/nebula-logger-plugin-development/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-plugin-development"><img src="https://agentmods.dev/badge/skills/jongpie/nebulalogger/nebula-logger-plugin-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, 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 58 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
- medium Prompt Injection · line 60 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
- medium Prompt Injection · line 67 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.00084 | $0.02400 |
| Opus 5.5 | $0.00034 | $0.00960 |
| Sonnet 5.5 | $0.00017 | $0.00480 |
| Haiku 4.5 | $0.00008 | $0.00240 |
Grade A, and why
nebula-logger-plugin-development 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 1mo 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Building Plugins for Nebula Logger
Package Compatibility
The plugin framework is only available in the unlocked package. The managed package (namespace Nebula) does not currently expose the plugin extension points.
If you plan to write plugins, install the unlocked package. See nebula-logger-install for the choice.
Note that LoggerPlugin, LoggerPlugin.Triggerable, LoggerPlugin.Batchable, LoggerTriggerableContext, and LoggerBatchableContext are all public (not global). Everywhere else in this skill collection, the guidance is "only rely on global" (see the "Supported API Surface" section of nebula-logger-instrumentation). The plugin framework is a deliberate exception: the extension points are public because they're only reachable inside the unlocked package's own compilation unit. As with any public surface, breaking changes are possible - pin plugins to a Nebula Logger version you've tested against and re-verify after upgrades.
Plugin Framework Overview
Nebula Logger's plugin framework lets you register Apex classes to run inside two extension points:
- Trigger extension point - Runs during
LoggerSObjectHandlerexecution onLogEntryEvent__e,Log__c,LogEntry__c,LogEntryTag__c,LoggerScenario__c, andLoggerTag__ctriggers. Use this to add fields, enrich data, or send external notifications when a log is created. - Batch extension point - Runs during
LogBatchPurgerexecution. Use this to archive logs to an external system, apply custom purge policies, or emit metrics on purged records before they're deleted.
Both extension points are driven by LoggerPlugin__mdt records. Adding a plugin means: writing an Apex class that implements the right interface (or both, if the plugin has trigger and batch responsibilities), then creating a LoggerPlugin__mdt record that points at it.
Strongly prefer Apex over Flow for both extension points. The framework technically supports Flow-based plugins via SObjectHandlerFlowName__c / BatchPurgerFlowName__c, but Flow support currently has known issues with no fixed ETA - it may be deprecated altogether in a future release. New plugins should implement the Apex interfaces below and leave the Flow fields on the LoggerPlugin__mdt record blank.
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.
- 1mo ago First seen · 124 lines · 84 tokens per session scan A 847592142cc0
nebula-logger-plugin-development is a skill published in the GitHub repository jongpie/NebulaLogger (972 stars, last pushed yesterday), licensed MIT. It adds 84 tokens to every session and 2,400 once invoked, about $0.0003 per session on Opus 5.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-performance
Performance optimization strategies for Salesforce B2C Commerce Cloud including caching, efficient data retrieval, index-friendly APIs, and job optimization. Use when asked about SFCC performance, caching strategies, or optimization.
sfcc-scapi-hooks
Guide for implementing SCAPI hooks in Salesforce B2C Commerce. Use this when asked to create SCAPI hooks, extend Shopper API endpoints, validate API requests, or modify API responses for headless commerce.
sfcc-security
Secure coding best practices for Salesforce B2C Commerce Cloud including CSRF protection, authentication, authorization, cryptography, and secrets management. Use when asked about SFCC security, input validation, or secure coding patterns.
sfcc-sfra-scss
Best practices for styling and theming SFRA storefronts using SCSS. Use when asked to create style overrides, theming, responsive layouts, or CSS customizations in SFCC.
sfcc-localserviceregistry
Guide for creating server-to-server integrations in Salesforce B2C Commerce using LocalServiceRegistry. Use this when asked to integrate external APIs, create HTTP services, implement OAuth flows, or configure service credentials.
sfcc-ocapi-hooks
Guide for implementing OCAPI hooks in Salesforce B2C Commerce. Use this when asked to create OCAPI hooks, extend API endpoints, validate API requests, or modify API responses.