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/adding-notesnpx skills add sabertaz/notes --skill adding-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.00080 | $0.00460 |
| Opus 5 | $0.00040 | $0.00230 |
| Sonnet 5 | $0.00016 | $0.00092 |
| Haiku 4.5 | $0.00008 | $0.00046 |
Grade A, and why
adding-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 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
Adding Notes
Identify the core concept from the user's content, find the best existing file and section, insert concisely.
Core Principle: Concept ≠ Example
The #1 mistake: treating the example subject as the topic.
User provides: systemctl cat paccache.service
❌ → new "paccache" section
✅ → existing "systemctl cat" section (paccache is just an example)
User provides: nginx.conf gzip settings
❌ → new "gzip-config.md"
✅ → existing web/nginx/ section
Ask yourself: Does this knowledge apply to any instance, or only this specific one? If "any" → put it with the tool/concept, not the example.
Workflow
- Identify concept — commands → the command; config → the tool; errors → the pattern; code → the feature
- Locate target —
Grep/Globfor the concept incontent/{ai,cs,language,programming,web}/. Prefer existing section > existing file new subsection > new file (last resort, ask user) - Insert — match surrounding language/style density. New files need frontmatter:
tags: [Domain, Topic]+sidebar_position. Available formats: KaTeX, Mermaid,:::tip,./figures/*.webp - Deduplicate — same concept better info → update; different angle → supplement; truly new → add
- Verify — concept not example ✓ no duplicates ✓ matching style ✓ frontmatter if new file ✓
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 · 38 lines · 80 tokens per session scan A f697e7acabf2
adding-notes is a skill published in the GitHub repository sabertaz/notes (48 stars, last pushed 17d ago), licensed MIT. It adds 80 tokens to every session and 460 once invoked, about $0.0004 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.