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/analyze-kbnpx skills add Abilityai/cornelius --skill analyze-kbgit 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/analyze-kb)<a href="https://agentmods.dev/skills/abilityai/cornelius/analyze-kb"><img src="https://agentmods.dev/badge/skills/abilityai/cornelius/analyze-kb.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.00017 | $0.01256 |
| Opus 5 | $0.00009 | $0.00628 |
| Sonnet 5 | $0.00003 | $0.00251 |
| Haiku 4.5 | $0.00002 | $0.00126 |
Grade A, and why
analyze-kb 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.
How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze the Obsidian knowledge base structure and regenerate a condensed, manageable analysis report.
Local Brain Search
Use Local Brain Search for all semantic search operations.
Scripts:
# Semantic search
resources/local-brain-search/run_search.sh "query" --limit 10 --json
# Find connections
resources/local-brain-search/run_connections.sh "Note Name" --json
# Get graph statistics
resources/local-brain-search/run_connections.sh --stats --json
# Find hub notes
resources/local-brain-search/run_connections.sh --hubs --json
# Find bridge notes
resources/local-brain-search/run_connections.sh --bridges --json
Follow these steps:
-
Get vault statistics using Local Brain Search:
resources/local-brain-search/run_connections.sh --stats --json -
List all notes with full directory tree using
Bashfind:find $VAULT_BASE_PATH/Brain -name "*.md" -type f | head -50 -
Use
Globto explore directory structure:- All notes:
Brain/**/*.md - Permanent notes:
Brain/02-Permanent/*.md - MOCs:
Brain/03-MOCs/*.md - Sources:
Brain/01-Sources/**/*.md
- All notes:
-
Read key hub notes from major clusters using
Readtool (Dopamine, Self/Buddhism, Decision-Making, Flow, etc.) -
Use Local Brain Search to identify hub notes and bridges:
resources/local-brain-search/run_connections.sh --hubs --json resources/local-brain-search/run_connections.sh --bridges --jsonFingerprint scope note:
--hubs/--bridgesare the cognitive-fingerprint axis. Scope enforcement is now ON (MEMORY_CONFIG['scope']['enforce']=True, since 2026-06-25; see SCOPE-IMPLEMENTATION-PLAN.md), so they compute on the core subgraph only (02-Permanent,03-MOCs,AI Extracted Notes,01-Sources). Document-Insights-inflated hubs (Dopamine/Flow) no longer appear; the true core hubs (MOC - Eight-Circuit, Decision Making, Gilbert, Tetlock, Hagen) surface.--statsstays whole-graph (it answers "how big is the store", not "who am I"). Note which mode is active when recording hubs. -
Pull BDG statistics for layer distribution and lifecycle phases:
resources/brain-graph/run_brain_graph.sh status --json -
Analyze thematic clusters, hierarchical organization, and conceptual architecture
-
Use
EditorWriteto update theknowledge-base-analysis.mdfile with a condensed report (target: ~600-800 lines max):- Executive summary with key statistics
- Hierarchical structure mapping (condensed)
- 6 major thematic hubs with hub nodes (core thesis + key notes only)
- Network properties and connectivity (metrics + critical bridges)
- Content topology and source analysis (top-tier influences only)
- Intellectual trajectory and maturity assessment (phases + current focus)
- Recommendations for enhancement (high priority only)
CRITICAL OUTPUT REQUIREMENTS:
- Length target: 600-800 lines maximum (50% of previous verbose reports)
- Prioritize: Core insights, actionable frameworks, critical statistics, key bridge notes
- Eliminate: Excessive examples, redundant explanations, verbose elaborations
- Focus: What's unique, what's actionable, what's growing, what's next
- Style: Bullet points over paragraphs, tables over lists where appropriate
- No duplication: Say things once, clearly, then move on
Generate a condensed, scannable, high-signal report that reveals the knowledge base's personality, cognitive fingerprint, and growth opportunities without overwhelming detail.
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 · 122 lines · 17 tokens per session scan A 6f85b58febab
analyze-kb is a skill published in the GitHub repository Abilityai/cornelius (105 stars, last pushed 12d ago), licensed MIT. It adds 17 tokens to every session and 1,256 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.
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…