nebula-logger-console

nebula-logger-console is a skill for Claude Code, Codex from jongpie/NebulaLogger. It costs 98 tokens per session (1,670 once invoked), scanned A, original, MIT.

A Salesforce interface for browsing and investigating Nebula Logger records without writing database queries by hand.

In plain words
What is it for?
Use it to filter log records, inspect entries and tags, navigate related records, manage logger settings, and investigate errors or asynchronous jobs.
Why use it?
It gives support staff, administrators, and developers ready-made views for finding logs and related entries in production.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Install

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.

agentmods
npx agentmods add skills/jongpie/nebulalogger/nebula-logger-console
Any agent
npx skills add jongpie/NebulaLogger --skill nebula-logger-console
Clone the repo
git clone --depth 1 https://github.com/jongpie/NebulaLogger

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for nebula-logger-console

README.md
[![agentmods](https://agentmods.dev/badge/skills/jongpie/nebulalogger/nebula-logger-console.svg)](https://agentmods.dev/skills/jongpie/nebulalogger/nebula-logger-console)
Your own site
<a href="https://agentmods.dev/skills/jongpie/nebulalogger/nebula-logger-console"><img src="https://agentmods.dev/badge/skills/jongpie/nebulalogger/nebula-logger-console.svg" alt="Measured on agentmods" height="20"></a>
Per session 98 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,670 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00098 $0.01670
Opus 5 $0.00049 $0.00835
Sonnet 5 $0.00020 $0.00334
Haiku 4.5 $0.00010 $0.00167

Measured 6d ago against content hash 09b3910523b3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

nebula-logger-console 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 6d 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.

skills/nebula-logger-console/SKILL.md · 100 lines

How it starts

The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Using the Nebula Logger Console

What the Console Is

The Logger Console is a Salesforce Lightning App shipped with Nebula Logger. It gives admins, support engineers, and developers a purpose-built place to browse logs without hand-writing SOQL against the log-management custom objects (Log__c, LogEntry__c, LogEntryTag__c, LoggerScenario__c, LoggerTag__c) every time something happens in production.

  • App API name: LoggerConsole.
  • Navigation entries include Log__c, LogEntry__c, LoggerScenario__c, LoggerTag__c, and LogEntryTag__c.
  • A utility bar (LoggerConsoleUtilityBar FlexiPage) surfaces a Logger Settings panel for editing the effective hierarchy record without leaving the console.

Standard List Views

Nebula Logger ships a broad set of list views across all five log-management custom objects so most day-one investigations don't require a custom view:

  • Log__c: AllLogs, AllOpenLogs, AllClosedLogs, AllResolvedLogs, AllLogsWithERROREntries, AllLogsWithERRORorWARNEntries, AllAsynchronousLogs, AllBatchLogs, AllChildLogs, AllImpersonatedLogs, AllRESTLogs, LogsToPurgeSoon, MyAssignedLogs, MyAssignedOpenLogs, MyGeneratedLogs.
  • LogEntry__c: All, AllERRORLogEntries, AllERRORandWARNLogEntries, AllApexLogEntries, AllComponentLogEntries, AllFlowLogEntries, AllHttpRequestLogEntries, AllHttpResponseLogEntries, AllRestRequestLogEntries, AllRestResponseLogEntries, AllExceptionLogEntries, AllImpersonatedLogEntries, AllOmniStudioLogEntries, MyGeneratedLogEntries.
  • LogEntryTag__c: All, AllImpersonatedLogEntryTags.
  • LoggerScenario__c: All, MyAssignedLoggerScenarios.
  • LoggerTag__c: All.

When investigating an incident, start with the pre-built views and narrow with column filters before creating a new custom list view.

Record Pages

Nebula Logger ships a dedicated FlexiPage for each user-facing log-management object. The LogEntryTag__c junction is browsed through its record page but doesn't have its own FlexiPage in the log-management folder - it's rendered with the standard record page layout.

Read the full file on GitHub · 100 lines

Changes

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.

  1. 6d ago First seen · 100 lines · 98 tokens per session scan A 09b3910523b3

Subscribe to this mod's changes

nebula-logger-console is a skill published in the GitHub repository jongpie/NebulaLogger (958 stars, last pushed today), licensed MIT. It adds 98 tokens to every session and 1,670 once invoked, about $0.0005 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.

Related

Other skills, from other repositories

sfcc-webdav-workflows

Practical guide for using WebDAV in Salesforce B2C Commerce Cloud for IMPEX transfers and log access. Use this when setting up WebDAV clients, debugging WebDAV permission issues, or designing automation that reads/writes files via WebDAV.

taurgis/sfcc-dev-mcp · 56 tokens

mcp-log-debugging

Skill "mcp-log-debugging" from taurgis/sfcc-dev-mcp, covering mcp log debugging skill, enable debug logs, locate the log directory, capture logs into workspace (safe for mcp tools) and what to look for.

taurgis/sfcc-dev-mcp · 0 tokens

sf-knowledge-salesforce-app-limits-cheatsheet

Apply Salesforce knowledge and best practices for Salesforce Developer Limits and Allocations Quick Reference.

Avinava/sf-documentation-knowledge · 27 tokens

triage-report

Decide whether a Portwood bug report is a real code defect or a template-authoring problem, before any code is written. Use when a user reports "the PDF looks wrong", a merge tag didn't resolve, an image is missing, a chart is distorted, or output doesn't match the template. Most reports are template issues.

Portwood-Global-Solutions/Portwood · 70 tokens

fix-merge-tag

Fix a Portwood merge-tag or parser bug correctly across all of its resolution paths. Use when changing tag parsing, section/loop tags, conditionals, aggregates, or chart buckets — a fix in one path silently does not reach the others.

Portwood-Global-Solutions/Portwood · 54 tokens

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.

taurgis/sfcc-dev-mcp · 43 tokens