helpers: Skill for Claude Code

.claude/skills/notebook.fix_packages/SKILL.md

notebook.fix_packages is a skill for Claude Code from causify-ai/helpers. It costs 16 tokens per session (991 once invoked), scanned A, original, Apache-2.0.

A workflow for keeping a project's Docker setup matched to a shared template and installing the Python packages that its Jupyter notebooks import.

In plain words
What is it for?
Use it to compare Docker and dependency files with a template, find packages used by notebooks, and install the needed Python packages.
Why use it?
It reduces differences between project containers and avoids missing-package errors when running notebooks.

Skill for Claude Code

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

This is causify-ai/helpers's own configuration. It tells Claude Code how to work on helpers itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything helpers configures →

Reuse

Borrowing it

Nothing to install: this file belongs to causify-ai/helpers. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/causify-ai/helpers/master/.claude/skills/notebook.fix_packages/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/causify-ai/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_packages

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/causify-ai/helpers/notebook.fix_packages"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/notebook.fix_packages.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 991 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.00016 $0.00991
Opus 5.5 $0.00006 $0.00396
Sonnet 5.5 $0.00003 $0.00198
Haiku 4.5 $0.00002 $0.00099

Measured 1mo ago against content hash 20ac3c51c41d, 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_packages 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.

.claude/skills/notebook.fix_packages/SKILL.md · 104 lines

How it starts

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

Goal

  • When creating Docker images for projects and tutorials, we want to
    • Try to use always the same Docker template image from the class_project to avoid replication of Docker containers
    • Install the needed packages in the notebooks to customize the container

Inputs

  • The user passes:
    • A pointer to a target directory <TARGET_DIR> (e.g., msml610/tutorials/L03_knowledge_representation) that was cloned from class_project/project_template
    • (Optional) pointers to Jupyter notebooks

Workflow

Use the Docker Container From the Project Teamplate

  • In the directory with the project (e.g., msml610/tutorials/L03_knowledge_representation) we want to use the same Dockerfile and requirements.txt as the corresponding files in class_project/project_template (so that the Docker container for the project is the same as the template used for class project)
  • If something needs to be added to the Docker image (e.g., a package that can't be installed with pip) then it's ok to add it to Dockerfile but it should be clearly commented why that package is needed

Discover All Packages Needed by the Notebook

  • A notebook's own import lines are not the full picture: each notebook is paired with a *_utils.py file (e.g., L03_06_logic_solvers.ipynb -> L03_06_logic_solvers_utils.py), and that file is imported with a line like:

    import L03_06_logic_solvers_utils as utils
    
  • Read the *_utils.py file (and any other local module it imports, transitively) and collect every third-party import / from ... import statement in it, not just the ones in the notebook itself

  • Map import names to their pip package name where they differ (e.g., cv2 -> opencv-python, sklearn -> scikit-learn, PIL -> Pillow, yaml -> PyYAML)

  • Diff this full package list against requirements.txt and Dockerfile: any package used by the notebook or its utils file that is missing from both is a bug, even if it happens to already be installed in whatever container was used to author the notebook

  • Add every missing package to requirements.txt (and to Dockerfile only if it can't be installed with pip, per ## Use the Docker Container from the Project Teamplate above)

Read the full file on GitHub · 104 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. 1mo ago First seen · 104 lines · 16 tokens per session scan A 20ac3c51c41d

Subscribe to this mod's changes

notebook.fix_packages is a skill published in the GitHub repository causify-ai/helpers (150 stars, last pushed today), licensed Apache-2.0. It adds 16 tokens to every session and 991 once invoked, about $0.0001 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-09-14.

Related

Other skills, from other repositories

azure-containerregistry-py

Manage container images, artifacts, and repositories in Azure Container Registry.

benjaminasterA/antigravity-awesome-skills · 0 tokens

airflow

Apache Airflow is a platform for programmatically authoring, scheduling, and monitoring workflows. Learn to write DAGs, use operators, set up connections, configure scheduling, and deploy with Docker Compose.

TerminalSkills/skills · 43 tokens

python-install-skill

An installation helper for Python 3, a programming language and runtime. It checks whether Python is already installed and supports package-manager or Docker-based installation on common operating systems.

jiushiwon/wg-skills · 49 tokens

docker_packaging

A set of rules and templates for packaging a Python MCP service in Docker. Docker packages an application and its dependencies into a repeatable container that can run on another machine.

fdueblab/Micro-Agent · 0 tokens

new-service

Scaffolds a new spec-driven Python service: a uv src-layout repo with the keystone DI/settings/entrypoint shells, Docker + compose + Liquibase migrator, and the vendored spec-core runtime modules, rendered by a deterministic script. Invoke with: /project-scaffold:new-service [--package PKG] [--python 3.12] [--port…

voro6yov/spec-driven-development · 109 tokens

python-containers

Python container optimization — slim images (not Alpine), virtualenv, multi-stage, pip/poetry/uv, musl gotchas (1GB to 120MB). Use when working with Python containers or optimizing image sizes.

laurigates/claude-plugins · 50 tokens