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/onebrain-ai/onebrain/consolidatenpx skills add onebrain-ai/onebrain --skill consolidategit clone --depth 1 https://github.com/onebrain-ai/onebrainWrote 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/onebrain-ai/onebrain/consolidate)<a href="https://agentmods.dev/skills/onebrain-ai/onebrain/consolidate"><img src="https://agentmods.dev/badge/skills/onebrain-ai/onebrain/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.1 | $0.00095 | $0.02331 |
| Opus 5 | $0.00048 | $0.01166 |
| Sonnet 5 | $0.00019 | $0.00466 |
| Haiku 4.5 | $0.00010 | $0.00233 |
Grade A, and why
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 6d 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Consolidate
Process your inbox and recent captures into your permanent knowledge base.
Step 1: Survey the Inbox
List all files in [inbox_folder]/ (excluding .gitkeep). For each file:
- Read the title and first few lines
- Note the date and main topics
Report: ────────────────────────────────────────────────────────────── 📥 Consolidate — {N} inbox items ──────────────────────────────────────────────────────────────
{filename}— {brief description}, {N tasks} tasks{filename}— {brief description}
Step 2: Let User Choose Scope
AskUserQuestion:
- question: "Which items do you want to process?"
- header: "Consolidate Scope"
- multiSelect: false
- options:
- label: "all", description: "Process all inbox items"
- label: "last N days", description: "Process items from the last N days (specify N)"
- label: "specific file", description: "Process a specific file (name it)"
- label: "just review", description: "Review without moving anything"
Step 2.5: Pre-classify (parallel)
Before processing, dispatch one Inbox Classifier agent (agents/inbox-classifier.md) per selected inbox note in parallel (run_in_background: false, mode: "bypassPermissions"). Pass each note's note_path, note_content, vault_root, knowledge_folder, resources_folder, areas_folder, and projects_folder. Wait for all results before proceeding to Step 3.
Store each result as the default routing recommendation for that note. If a classifier call fails or returns an empty result, proceed without a recommendation for that note.
Step 3: Process Each Selected Item
For each item:
3a. Analyze
Read the file fully. Use the pre-classification from Step 2.5 as the starting point. Confirm or adjust based on your own reading:
- What type of knowledge this is (insight, reference, idea, project note, area)
- What existing notes it relates to (search via the search tools if available, otherwise Glob
[knowledge_folder]/**/*.md,[resources_folder]/**/*.md,[projects_folder]/**/*.md,[areas_folder]/**/*.md). For search-tool results, only keep candidates withrerank_score ≥ 0.30(prefer≥ 0.60) — drop anything below 0.30. - Whether it deserves its own note or should be merged into an existing one
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.
- 6d ago First seen · 220 lines · 95 tokens per session scan A b5c856cab15c
consolidate is a skill published in the GitHub repository onebrain-ai/onebrain (26 stars, last pushed 8d ago), licensed Apache-2.0. It adds 95 tokens to every session and 2,331 once invoked, about $0.0005 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
llm-wiki
Build and maintain a persistent, interlinked Obsidian-compatible markdown wiki using Karpathy's LLM Wiki pattern. Extension-backed with auto-generated metadata, guardrails, and 14 custom tools (+3 opt-in agent-trajectory tools).
link-memory
Use after important user-approved decisions, when durable context should be proposed or reviewed, and for explicit Link memory lifecycle work: remember, recall, review, update, archive, restore, forget, or explain local memories through the CLI without requiring MCP.
link-retrieve
Use before answering work that may depend on user memory, project history, source-backed notes, or prior decisions; retrieve compact Link context through the CLI without loading the whole wiki or requiring MCP.
link-ingest
Use when raw files are present, source pages look stale, or a user asks to ingest notes into Link; refresh source-backed wiki pages, propose memories, and validate updates through the CLI without MCP.
lint-brain
Run health checks over the brain vault - find orphan notes, broken wikilinks, missing frontmatter, stale projects, and missing cross-links. Use when asked to "lint the brain", "health check", "vault hygiene", or "/lint-brain".
ingest-article
Ingest an article from a URL or raw text into the brain vault. Extracts key knowledge, determines placement, creates or updates notes, and links to relevant projects. Use when the user shares a URL or text and wants to absorb it into their knowledge base.