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 gpsaggese/helpers --skill notebook.split_header_cellsgit clone --depth 1 https://github.com/gpsaggese/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/gpsaggese/helpers/notebook.split_header_cells)<a href="https://agentmods.dev/skills/gpsaggese/helpers/notebook.split_header_cells"><img src="https://agentmods.dev/badge/skills/gpsaggese/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/gpsaggese/helpers/notebook.split_header_cells"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/notebook.split_header_cells.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00436 |
| Opus 5.5 | $0.00005 | $0.00174 |
| Sonnet 5.5 | $0.00003 | $0.00087 |
| Haiku 4.5 | $0.00001 | $0.00044 |
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 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.
What it actually says
Goal
- Split each markdown cell in a Jupyter notebook so it has at most one header
Workflow
Split Markdown Cells
- Make sure each markdown cell has at most one header and some text
- 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
- Bad (there are 3 headers in the same cell: one H1, one H2, one H3)
Remove Empty Lines
- Remove empty lines at the start or end of a markdown cell
- Bad (blank lines around the header)
# %% [markdown] # Part 3: Composition Examples - Good (no blank lines around the header)
# %% [markdown] # Part 3: Composition Examples
- Bad (blank lines around the header)
Sync with Jupytext
- At the end, run
jupytext --syncto update the paired Python notebook, per# 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.
- yesterday First seen · 67 lines · 13 tokens per session scan A 17a5cff1e9e2
notebook.split_header_cells is a skill published in the GitHub repository gpsaggese/helpers (158 stars, last pushed today), licensed Apache-2.0. It adds 13 tokens to every session and 436 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-11-06.
notebook.split_header_cells compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| notebook.split_header_cellsgpsaggese/helpers | Skill | 158 | today | Apache-2.0 | A | 13 | Claude Code |
| imagegenopenai/codex | Skill | 134k | today | Apache-2.0 | A | 113 | Codex |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | today | MIT | A | 200 | Claude Code, Codex |
| playwright-climicrosoft/playwright | Skill | 99k | today | Apache-2.0 | A | 19 | Claude Code |
| systematic-debuggingobra/superpowers | Skill | 314k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |
| chat-pet-sprite-creationmicrosoft/vscode | Skill | 195k | today | MIT | A | 53 | Claude Code, Codex |