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/laat/mor/notes-consolidatenpx skills add laat/mor --skill notes-consolidategit clone --depth 1 https://github.com/laat/morWrote 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/laat/mor/notes-consolidate)<a href="https://agentmods.dev/skills/laat/mor/notes-consolidate"><img src="https://agentmods.dev/badge/skills/laat/mor/notes-consolidate.svg" alt="Measured on agentmods" 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 | $0.00033 | $0.00785 |
| Opus 5 | $0.00016 | $0.00392 |
| Sonnet 5 | $0.00007 | $0.00157 |
| Haiku 4.5 | $0.00003 | $0.00078 |
Grade A, and why
notes-consolidate 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 4d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apply a natural language instruction across a set of notes, handling cross-reference updates automatically.
Examples
/notes-consolidate all pipeline notes should have Pipeline prefix in title
/notes-consolidate normalize fsharp tags — use "fsharp" not "f#"
/notes-consolidate add cross-references between related pipeline notes
/notes-consolidate merge the two ID model notes into one
/notes-consolidate remove the todo tag from completed items
Steps
-
Parse the instruction: Identify:
- Scope — which notes to target (tag filter, search query, explicit IDs, or "all")
- Action — what to do (rename, retag, add links, merge, update content, delete)
-
Find target notes: Use
morMCP tools to find the notes:notes_listwith tag/type filters for broad scopesnotes_searchfor query-based scopesnotes_readfor explicit IDs
Read each target note's full content to understand what changes are needed.
-
Plan changes: For each target note, determine what needs to change. Present the plan to the user:
- List each note and what will change (title, tags, content, etc.)
- If merging: show which notes combine and which get deleted
- If adding cross-references: show which links will be added where
- Show total count: "X notes will be updated, Y unchanged"
-
Ask for approval before making any changes.
-
Execute changes: Apply updates one at a time using
notes_update. For each change:- Update the note
- If the change affects cross-references (title rename, ID change from merge, deletion), update all notes that link to it
-
Handle merges (when the instruction is to combine notes):
- Draft merged content — deduplicate, organize by topic, preserve all unique details
- Create the merged note with
notes_create - Update all backlinks in other notes to point to the new ID
- Remove the original source notes with
notes_remove - Remove
mor:links between source notes (they'd be self-references)
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.
- 4d ago First seen · 74 lines · 33 tokens per session scan A 201a3705071e
notes-consolidate is a skill published in the GitHub repository laat/mor (2 stars, last pushed 4d ago), licensed MIT. It adds 33 tokens to every session and 785 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-31.
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…