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/changelog-protocolnpx skills add Abilityai/cornelius --skill changelog-protocolgit clone --depth 1 https://github.com/Abilityai/corneliusWrote 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/abilityai/cornelius/changelog-protocol)<a href="https://agentmods.dev/skills/abilityai/cornelius/changelog-protocol"><img src="https://agentmods.dev/badge/skills/abilityai/cornelius/changelog-protocol.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.00035 | $0.00517 |
| Opus 5 | $0.00017 | $0.00259 |
| Sonnet 5 | $0.00007 | $0.00103 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
changelog-protocol 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 5d 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.
What it actually says
Changelog Protocol
All sub-agents MUST create separate dated changelog files after each significant session.
File Location & Naming
- Directory:
Brain/05-Meta/Changelogs/ - Naming Format:
CHANGELOG - [Session Type] YYYY-MM-DD.md - Examples:
CHANGELOG - Auto-Discovery Sessions 2025-10-25.mdCHANGELOG - Connection Discovery Session 2025-10-24.mdCHANGELOG - Vault Management Session 2025-10-26.mdCHANGELOG - Insight Extraction Session 2025-10-27.md
Timestamp Requirements
MANDATORY: Before starting any session, call:
date '+%Y-%m-%d %H:%M:%S %Z'
Include this timestamp at the top of the changelog file. Use the date from this command in the filename.
Changelog Content Structure
Each changelog file must include:
- Session header with date, time, and session type
- Session overview with key statistics
- Major discoveries/connections/changes documented in detail
- Emergent patterns or meta-insights
- Synthesis opportunities identified
- Session statistics (notes analyzed, connections found, etc.)
- Recommended next actions
When to Create Changelogs
| Agent | Trigger |
|---|---|
| Auto-Discovery Agent | After every discovery session (mandatory) |
| Connection Finder Agent | After every connection mapping session (mandatory) |
| Vault Manager Agent | After significant CRUD operations affecting 3+ notes |
| Insight Extractor Agent | After extracting insights from significant content |
Dual Logging System
- Dated files: Individual session logs in
/05-Meta/Changelogs/folder (primary, detailed) - Master CHANGELOG.md: Summary entries in
/Brain/CHANGELOG.md(secondary, brief)
The dated changelog files are the primary record - comprehensive and detailed. The master CHANGELOG.md serves as a quick reference index with brief entries pointing to the detailed session files.
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.
- 5d ago First seen · 57 lines · 35 tokens per session scan A 6b66bc5d5746
changelog-protocol is a skill published in the GitHub repository Abilityai/cornelius (106 stars, last pushed 12d ago), licensed MIT. It adds 35 tokens to every session and 517 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…