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/deep-researchnpx skills add Abilityai/cornelius --skill deep-researchgit 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.00021 | $0.04962 |
| Opus 5 | $0.00010 | $0.02481 |
| Sonnet 5 | $0.00004 | $0.00992 |
| Haiku 4.5 | $0.00002 | $0.00496 |
Grade A, and why
deep-research 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 3d 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 — 622 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deep Research & Knowledge Integration Pipeline
You are orchestrating a fully autonomous research → extraction → connection discovery workflow to expand the knowledge base with cutting-edge insights.
Input Processing
User Input: $ARGUMENTS
Execution Modes:
- Directed Mode - User specifies topic(s):
$ARGUMENTS = "neuroscience of habits"or$ARGUMENTS = "multi-agent systems, safety alignment" - Autonomous Mode - You select topics:
$ARGUMENTS = ""or$ARGUMENTS = "auto"
Mission
Execute a complete 3-phase autonomous research pipeline:
- RESEARCH - Gather cutting-edge papers and developments
- EXTRACT - Pull unique insights from research findings
- CONNECT - Map connections to existing knowledge base
Critical Requirement: ALL extracted insights MUST be stored in Document Insights folder structure to keep separate from main Brain.
Phase 1: Topic Selection & Research Planning
A. If User Provided Topic(s) (Directed Mode)
- Parse
$ARGUMENTSfor topic(s) - Validate topics are research-worthy
- Plan research scope for each topic
B. If Autonomous Mode
Analyze knowledge base to identify research opportunities:
-
Read knowledge base analysis:
cat knowledge-base-analysis.md -
Check recent activity:
ls -lt Brain/Document\ Insights/ | head -10 -
Identify gaps based on:
- Underrepresented domains in knowledge-base-analysis.md
- Missing connections flagged in recent changelogs
- Emerging themes from existing insights
- User's recent work patterns
- CLAUDE.md priorities and future directions
-
Select 1-3 research topics that would:
- Fill identified gaps
- Build on existing strengths (e.g., Buddhism-Neuroscience-AI triangle)
- Connect underexplored domains
- Add empirical validation to intuitive frameworks
- Challenge or extend current thinking
Examples of Good Topic Selection:
- "Neuroscience of habits and behavior change" (if habit formation underrepresented)
- "Collective intelligence and swarm behavior" (if group dynamics missing)
- "Embodied cognition and interoception" (if embodiment gap identified)
- "Complexity science and emergence" (if systems thinking needed)
- "Creativity neuroscience and insight generation" (if creative process mechanics missing)
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.
- 3d ago First seen · 622 lines · 21 tokens per session scan A 30e041d693fa
deep-research is a skill published in the GitHub repository Abilityai/cornelius (104 stars, last pushed 10d ago), licensed MIT. It adds 21 tokens to every session and 4,962 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…