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/summarizenpx skills add onebrain-ai/onebrain --skill summarizegit clone --depth 1 https://github.com/onebrain-ai/onebrainWhat 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.00078 | $0.01306 |
| Opus 5 | $0.00039 | $0.00653 |
| Sonnet 5 | $0.00016 | $0.00261 |
| Haiku 4.5 | $0.00008 | $0.00131 |
Grade A, and why
summarize 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Summarize
Fetch a URL and create a structured summary note in your resources folder.
Usage: /summarize [url]
Step 1: Get the URL
If provided after the command, use it directly.
If not, ask:
What URL do you want to summarize?
Step 2: Check Bookmarks
Grep [resources_folder]/Bookmarks.md for the URL. If found, note it silently : you will offer to remove it after the summary note is saved (Step 7).
Step 3: Ask for Context
Optional but helpful : ask:
Why are you saving this? (e.g., research for a project, reference for later, interesting read)
This context shapes how the summary is framed.
Step 4: Fetch and Read
Fetch the URL content. If it fails:
I couldn't fetch that URL. You can paste the content directly and I'll summarize it.
Read the full page content.
Step 5: Extract Key Information
Identify:
- Title of the article/page
- Author and publication date (if available)
- Core thesis or main point
- Key arguments or findings (3-7 points)
- Memorable quotes (1-3 if applicable)
- Actionable takeaways (if any)
- Content type: article, documentation, paper, blog post, video transcript, etc.
Step 6: Choose Subfolder and Save
Resolve subfolder:
- Glob existing subfolders in
[resources_folder]/*/ - Suggest a kebab-case subfolder based on the article's topic (max 2 levels, e.g.
productivity/tools) - Present to user: "I'd file this under
[resources_folder]/[suggested-path]/. OK?" - Use confirmed path for file creation.
Create the summary note at [resources_folder]/[subfolder]/[Article Title].md:
---
tags: [summary, topic-tag]
created: YYYY-MM-DD
source: /summarize
url: [URL]
author: [Author Name]
published: [Publication date if known]
---
# [Article Title]
> **Source:** [URL]
> **Saved:** YYYY-MM-DD
> **Why I saved this:** [User's context, if provided]
## Summary
[2-3 sentence summary of the main point]
## Key Points
- [Point 1]
- [Point 2]
- [Point 3]
## Notable Quotes
> "[Quote]"
> : [Author/Source]
## My Takeaways
[Leave blank for the user to fill in, or ask if they want to add any now]
## Related
[[Link to related vault notes]]
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 · 169 lines · 78 tokens per session scan A 76447a173e20
summarize is a skill published in the GitHub repository onebrain-ai/onebrain (25 stars, last pushed 5d ago), licensed Apache-2.0. It adds 78 tokens to every session and 1,306 once invoked, about $0.0004 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
excalidraw-diagram
Generate Excalidraw diagrams from text content. Supports three output modes - Obsidian (.md), Standard (.excalidraw), and Animated (.excalidraw with animation order). Triggers on "Excalidraw", "diagram", "standard excalidraw", "animate".
mermaid-visualizer
Transform text content into professional Mermaid diagrams for presentations and documentation. Use when users ask to visualize concepts, create flowcharts, or make diagrams from text. Supports process flows, system architectures, comparisons, mindmaps, and more with built-in syntax error prevention.
qmd
Search the vault using QMD semantic search. Use PROACTIVELY before reading files. Preference order: (1) MCP tools — mcpqmdquery, mcpqmdget, mcpqmdmultiget, mcpqmdstatus — if they appear in your tool menu, use them first; (2) CLI qmd --index ... as fallback; (3) Grep/Glob only when QMD is not installed. Trigger…
obsidian-cli
Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their…
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).
deeppapernote
Generate a high-quality deep-reading note for a single paper and write it into an Obsidian-style vault. Use when the user gives a paper title, DOI, URL, arXiv ID, Zotero item, or local PDF and wants a polished Markdown note with strong structure, evidence-based analysis, and figure placeholders.