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/abilityai/cornelius/integrate-recent-notesnpx skills add Abilityai/cornelius --skill integrate-recent-notesgit clone --depth 1 https://github.com/Abilityai/corneliusWhat 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.00024 | $0.00988 |
| Opus 5 | $0.00012 | $0.00494 |
| Sonnet 5 | $0.00005 | $0.00198 |
| Haiku 4.5 | $0.00002 | $0.00099 |
Grade A, and why
integrate-recent-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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integrate Recent Notes
Find recently created notes and map their connections to the existing knowledge base.
Purpose
New notes often sit unconnected. This playbook identifies notes from the last 14 days and discovers how they integrate with existing knowledge.
State Dependencies
| Source | Location | Read | Write | Description |
|---|---|---|---|---|
| Permanent Notes | Brain/02-Permanent/ |
✓ | Recent notes source | |
| AI Extracted Notes | Brain/AI Extracted Notes/ |
✓ | Recent notes source | |
| Document Insights | Brain/Document Insights/ |
✓ | Recent notes source | |
| Book scopes | Brain/Books/ |
✓ | Recent notes source (per-book scopes) | |
| Local Brain Search | resources/local-brain-search/ |
✓ | Connection discovery | |
| Session Changelogs | Brain/05-Meta/Changelogs/ |
✓ | Integration report |
Prerequisites
- Local Brain Search index up-to-date (
/refresh-index)
Process
Step 1: Find Recent Notes
Find notes modified in the last 14 days:
find Brain/02-Permanent -name "*.md" -mtime -14 -type f
find Brain/AI\ Extracted\ Notes -name "*.md" -mtime -14 -type f
find Brain/Document\ Insights -name "*.md" -mtime -14 -type f
find Brain/Books -name "*.md" -mtime -14 -type f
Compile list of recent notes.
Step 2: Get Current Date
date '+%Y-%m-%d'
Step 3: Analyze Connections for Each
For each recent note:
- Extract note title from filename
- Run connection discovery (wide read-scope: recent notes live in 00-Inbox /
Document Insights / Books / 05-Meta - core-only would fail to resolve the note
itself or its non-core neighbors once scope enforcement is on):
BRAIN_READ_SCOPE=core,Books,document-insights,meta,inbox,output resources/local-brain-search/run_connections.sh "Note Title" --json - Record top 5 connections with similarity scores
- Check BDG layer classification:
resources/brain-graph/run_brain_graph.sh inspect "Note Title" --json
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 · 128 lines · 24 tokens per session scan A cd09c00132d3
integrate-recent-notes is a skill published in the GitHub repository Abilityai/cornelius (104 stars, last pushed 9d ago), licensed MIT. It adds 24 tokens to every session and 988 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…