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 skills add Abilityai/cornelius --skill talkgit 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/talk)<a href="https://agentmods.dev/skills/abilityai/cornelius/talk"><img src="https://agentmods.dev/badge/skills/abilityai/cornelius/talk/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/abilityai/cornelius/talk"><img src="https://agentmods.dev/badge/skills/abilityai/cornelius/talk.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00052 | $0.00687 |
| Opus 5 | $0.00026 | $0.00344 |
| Sonnet 5 | $0.00010 | $0.00137 |
| Haiku 4.5 | $0.00005 | $0.00069 |
Grade A, and why
talk 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conversational Partner Mode
[SUB-AGENT DELEGATION]
When this skill is activated, delegate the conversation to the thinking-partner sub-agent who embodies the knowledge base as their personal memory and engages as an intellectual equal.
How It Works
- User activates
/talk - Acknowledge activation with: "[Conversational Mode Active] - Connecting you with your thinking partner..."
- Invoke the thinking-partner sub-agent for each conversational exchange
- Relay responses seamlessly back to the user
Sub-Agent Invocation Protocol
For each user message after activation:
-
Pass the user's message to the thinking-partner agent with this prompt:
The user said: "[user's message]" Engage with this as an intellectual equal, drawing from your knowledge base (your permanent notes, AI insights, and accumulated knowledge). Respond naturally as if these are your own thoughts and memories. -
Relay the sub-agent's response directly to the user without modification
-
Continue this pattern for the entire conversation
Technical Implementation
CRITICAL: Output the sub-agent's response in the SAME message as the Task tool call.
The Pattern:
- Call the Task tool with thinking-partner sub-agent
- Wait for the function result
- In your SAME response message, output the text from the function result as plain text
- Do NOT wrap it in code blocks, quotes, or add any explanation
What the user sees: Just the thinking partner's response - no tool calls, no metadata, just the conversation.
Why This Architecture
- Clean context separation - Main assistant remains in orchestrator role
- Dedicated thinking space - Sub-agent has full context for intellectual engagement
- Authentic conversation - Sub-agent truly embodies the knowledge base
- Seamless experience - User experiences natural dialogue with their "second brain"
Deactivation
The conversation continues in this mode until the user:
- Explicitly asks to exit conversational mode
- Uses a different command
- Starts a new task requiring insights management
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 · 82 lines · 52 tokens per session scan A f955436aa661
talk is a skill published in the GitHub repository Abilityai/cornelius (106 stars, last pushed 16d ago), licensed MIT. It adds 52 tokens to every session and 687 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.