notebook.fix_logging

notebook.fix_logging is a skill for Claude Code from gpsaggese/helpers. It costs 10 tokens per session (446 once invoked), scanned A, original, Apache-2.0.

A notebook logging setup workflow for Jupyter notebooks, which are documents that combine executable code with notes and output. It applies the project's standard initialization and connects notebook, utility, and selected third-party loggers to notebook output.

In plain words
What is it for?
Use it to update notebook setup, synchronize the paired Python file with Jupytext, and route relevant log messages to the notebook's output.
Why use it?
It prevents inconsistent logging setup across notebooks and avoids conflicting initialization methods such as basic global logging configuration.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; reads .claude/ paths.

Good fit Use it to update notebook setup, synchronize the paired Python file with Jupytext, and route relevant log messages to the notebook's output.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gpsaggese/helpers/notebook.fix_logging
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.

Any agent
npx skills add gpsaggese/helpers --skill notebook.fix_logging
Clone the repo
git clone --depth 1 https://github.com/gpsaggese/helpers

Made for: Claude Code.

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 notebook.fix_logging

README.md
[![agentmods](https://agentmods.dev/badge/skills/gpsaggese/helpers/notebook.fix_logging/github.svg)](https://agentmods.dev/skills/gpsaggese/helpers/notebook.fix_logging)
Your own site
<a href="https://agentmods.dev/skills/gpsaggese/helpers/notebook.fix_logging"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/notebook.fix_logging/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.

agentmods 80×15 button for notebook.fix_logging

Your own site · 80×15
<a href="https://agentmods.dev/skills/gpsaggese/helpers/notebook.fix_logging"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/notebook.fix_logging.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 10 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 446 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00010 $0.00446
Opus 5.5 $0.00004 $0.00178
Sonnet 5.5 $0.00002 $0.00089
Haiku 4.5 $0.00001 $0.00045

Measured yesterday against content hash a35b4e587d5f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

notebook.fix_logging 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.

.claude/skills/notebook.fix_logging/SKILL.md · 56 lines

What it actually says

Goal

  • Implement the instructions in .claude/skills/notebook.rules.md under ## Use Standard Template Structure

  • Use the structure from .claude/templates/notebook.template.py for notebook initialization

  • Use display

  • The local utility *_utils.py should have a function like

    import helpers.hnotebook as hnotebo
    
    def init_loggers(notebook_log: logging.Logger) -> None:
        """
        Wire the notebook logger into the utils logger.
    
        :param notebook_log: logger owned by the notebook
        """
        hnotebo.init_loggers(notebook_log, utils_log=_LOG)
    
    • hnotebo.init_loggers() already calls config_notebook(), initializes hdbg at INFO level, and redirects the notebook and utils loggers to print
    • For a third-party logger (e.g., causalml), redirect it inside init_loggers() with hnotebo.set_logger_to_print():
      hnotebo.set_logger_to_print(logging.getLogger("causalml"))
      
  • The last setup cell in the notebook calls utils.init_loggers(_LOG), not logging.basicConfig() or hdbg.init_logger()

Workflow

Sync Notebook

  • At the end, sync the paired .py file with Jupytext following the conventions in # Code Architecture and Responsibility -> ## Utilities vs. Notebook Responsibilities in .claude/skills/notebook.rules.md

Conventions

  • Always follow the conventions and guidelines in .claude/skills/notebook.rules.md

Verification

  • Confirm the notebook init cell matches .claude/templates/notebook.template.py
  • Confirm utils.init_loggers() is called and log messages print in the notebook
  • Confirm the .ipynb and paired .py file are in sync via Jupytext
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. yesterday First seen · 56 lines · 10 tokens per session scan A a35b4e587d5f

Subscribe to this mod's changes

notebook.fix_logging is a skill published in the GitHub repository gpsaggese/helpers (158 stars, last pushed today), licensed Apache-2.0. It adds 10 tokens to every session and 446 once invoked, about $0.0000 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-11-06.

Related

notebook.fix_logging compared with skills from other repositories

notebook.fix_logging next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
notebook.fix_logginggpsaggese/helpersSkill158todayApache-2.0A10Claude Code
content-hash-cache-patternaffaan-m/ECCSkill299ktodayMITA30Claude Code, Kiro
python-releaseComposioHQ/composioSkill31ktodayMITA53Claude Code, Codex
python-cli-ops0xDarkMatter/claude-modsSkill79todayMITA35Claude Code
python-projectmajiayu000/spellbookSkill2903d agoMITC43Claude Code, Codex
temp-file-python-analysisfabioc-aloha/Alex_Skill_MallSkill5todayMITA14Claude Code, Codex
uv-workflowbahayonghang/my-ai-cli-toolkitSkill179d agoMITA57Claude Code