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 agentmods add skills/sabertaz/notes/splitting-notesnpx skills add sabertaz/notes --skill splitting-notesgit clone --depth 1 https://github.com/sabertaz/notesWhat 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 | $0.00043 | $0.01288 |
| Opus 5 | $0.00022 | $0.00644 |
| Sonnet 5 | $0.00009 | $0.00258 |
| Haiku 4.5 | $0.00004 | $0.00129 |
Grade A, and why
splitting-notes 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Splitting Notes
Overview
Split large monolithic note files into focused, single-topic files with index-based navigation. Reduces cognitive load and improves discoverability through progressive grouping.
When to Use
digraph when_refactor {
"Note file size > 1000 lines?" [shape=diamond];
"Topics mixing unrelated concepts?" [shape=diamond];
"Hard to find specific information?" [shape=diamond];
"Refactor notes" [shape=box];
"Keep as-is" [shape=box];
"Note file size > 1000 lines?" -> "Refactor notes" [label="yes"];
"Note file size > 1000 lines?" -> "Topics mixing unrelated concepts?" [label="no"];
"Topics mixing unrelated concepts?" -> "Refactor notes" [label="yes"];
"Topics mixing unrelated concepts?" -> "Hard to find specific information?" [label="no"];
"Hard to find specific information?" -> "Refactor notes" [label="yes"];
"Hard to find specific information?" -> "Keep as-is" [label="no"];
}
Use when:
- Note files exceed 1000 lines
- Single file mixes unrelated topics
- Navigation and search are difficult
- Content needs better organization
Don't use when:
- Files are already under 500 lines
- Topics are tightly coupled
- Splitting would harm coherence
Prerequisite
Complex multi-step refactoring - Must complete planning phase first.
If not currently in plan mode, invoke EnterPlanMode before starting.
- In plan mode: Complete analysis and create migration plan
- After plan mode: Execute split and verification
Core Pattern
Before - Monolithic file:
content/topic/large-file.md (1500+ lines)
├── H2 Chapter 1
├── H2 Chapter 2
├── H2 Chapter 3
└── ...10+ more sections
After - Modular structure:
content/topic/
├── topic.md (index, ~50 lines)
├── chapter-1.md (~200 lines)
├── chapter-2.md (~150 lines)
├── chapter-3.md (~180 lines)
└── ...remaining chapters
See examples.md for complete walkthroughs of:
- Simple split (300 lines, Python)
- Medium split (850 lines, Vue)
- Complex split (1500 lines, React)
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 158 lines · 43 tokens per session scan A 4c7ef43b425a
splitting-notes is a skill published in the GitHub repository sabertaz/notes (48 stars, last pushed 18d ago), licensed MIT. It adds 43 tokens to every session and 1,288 once invoked, about $0.0002 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.
Other skills, from other repositories
electron-node-upgrade
Guide for performing Node.js version upgrades in the Electron project. Use when working on the roller/node/main branch to fix patch conflicts during e sync --3. Covers the patch application workflow, conflict resolution, analyzing upstream Node.js changes, building, running the Node.js test suite, and proper commit…
electron-chromium-upgrade
Guide for performing Chromium version upgrades in the Electron project. Use when working on the roller/chromium/main branch to fix patch conflicts during e sync --3. Covers the patch application workflow, conflict resolution, analyzing upstream Chromium changes, and proper commit formatting for patch fixes.
chrome-release-verify
End-to-end Chrome security backport for an Electron release branch. Given a Chrome Releases blog URL and a branch (e.g. 41-x-y), determines which CVE fixes are missing from the actual synced source, writes the cherry-pick patches locally, validates them with e sync --3 + lint --patches, then pushes a single PR. Use…
triage-prs
Triage open electron/electron pull requests by CI check status — lists PRs that are green/passing, failing, still pending, or have no checks at all, annotated with their Status on the "PR Triage" project board and with the new-pr label. Can scope to a single named check, e.g. PRs whose "faraday/cage" check is pending.…
chrome-release-cls
Given a Chrome Releases blog post URL (chromereleases.googleblog.com), extract every CVE/bug and find the underlying Gerrit CL that fixed it by searching the local Chromium checkout and sub-repos. Use when asked to map Chrome security release notes to fixing CLs, or to find which commits correspond to CVEs in a Chrome…
preline-mcp
Add, integrate, or build Preline UI components and blocks into HTML files via the Preline MCP server. Use when the user mentions "preline", says "/preline", asks to add a UI component, or requests a Preline block (a ready-made page section) using Preline UI.