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 causify-ai/helpers --skill notebook.split_header_cellsgit clone --depth 1 https://github.com/causify-ai/helpersWrote 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/causify-ai/helpers/notebook.split_header_cells)<a href="https://agentmods.dev/skills/causify-ai/helpers/notebook.split_header_cells"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/notebook.split_header_cells/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/causify-ai/helpers/notebook.split_header_cells"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/notebook.split_header_cells.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 Excessive Agency · line 3 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00013 | $0.00492 |
| Opus 5.5 | $0.00005 | $0.00197 |
| Sonnet 5.5 | $0.00003 | $0.00098 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
notebook.split_header_cells 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.
What it actually says
Goal
- Split each markdown cell in a Jupyter notebook so it contains at most one header
Workflow
Split Markdown Cells
- Make sure that each markdown cell in a Jupyter notebook contains at most one
header and some text, but not more than one header
- Bad (there are 3 headers in the same cell: one H1, one H2, one H3)
# %% [markdown] # Part 3: Composition Examples ## Example 1: Minimal End-to-End Workflow Rain -> Sprinkler -> Grass Wet ### Mental Model - Good (each header is in a different cell)
# %% [markdown] # Part 3: Composition Examples # %% [markdown] ## Example 1: Minimal End-to-End Workflow Rain -> Sprinkler -> Grass Wet # %% [markdown] ### Mental Model - Do not change the content of the markdown text besides splitting cells into multiple ones
- Bad (there are 3 headers in the same cell: one H1, one H2, one H3)
Remove Empty Lines
- Remove empty lines at the beginning or end of a markdown cell
- Bad (there are two headers in the same cell, one H1 and one H2)
# %% [markdown] # Part 3: Composition Examples - Good (each header is in a different cell)
# %% [markdown] # Part 3: Composition Examples
- Bad (there are two headers in the same cell, one H1 and one H2)
Sync with Jupytext
- At the end of the transformation, run
jupytext --syncto update the Python paired notebook, following the conventions in# Code Architecture and Responsibility->## Utilities vs. Notebook Responsibilitiesin.claude/skills/notebook.rules.md
Constraints
- Do not change or remove any Python code cell
- Do not change the content of the markdown text besides splitting cells
Verification
- Confirm no markdown cell contains more than one header
- Confirm every Python code cell is unchanged
- Confirm the
.ipynband paired.pyfile are in sync via Jupytext
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 Changed · +9 lines · -2 tokens per session e74561a285e2
- 1mo ago First seen · 63 lines · 15 tokens per session scan A 43c2bd4f8247
notebook.split_header_cells is a skill published in the GitHub repository causify-ai/helpers (152 stars, last pushed today), licensed Apache-2.0. It adds 13 tokens to every session and 492 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-03.
Other skills, from other repositories
content-hash-cache-pattern
Cache expensive file processing results using SHA-256 content hashes — path-independent, auto-invalidating, with service layer separation.
python-release
Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes. Use for Python release process work or dependency pin bumps; do not use for ordinary Python feature implementation.
python-cli-ops
CLI application patterns for Python. Triggers on: cli, command line, typer, click, argparse, terminal, rich, console, terminal ui.
python-project
Modern Python project architecture guide for 2025. Use when creating Python projects (APIs, CLI, data pipelines). Covers uv, Ruff, Pydantic, FastAPI, and async patterns.
uv-workflow
Use when a coding agent needs to run Python code, modules, one-liners, tools, tests, or standalone scripts through uv, or create and maintain PEP 723 scripts with uv init/add/remove --script. Avoid direct python/python3 shell entrypoints.
temp-file-python-analysis
Inline Python in shell scripts has quoting issues.