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/digestnpx skills add onebrain-ai/onebrain --skill digestgit 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/digest)<a href="https://agentmods.dev/skills/onebrain-ai/onebrain/digest"><img src="https://agentmods.dev/badge/skills/onebrain-ai/onebrain/digest.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.00101 | $0.01749 |
| Opus 5 | $0.00051 | $0.00874 |
| Sonnet 5 | $0.00020 | $0.00350 |
| Haiku 4.5 | $0.00010 | $0.00175 |
Grade A, and why
digest 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 4d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Digest
Compose a compact morning digest from configurable sections and deliver it per the
Automated-profile output convention (INSTRUCTIONS.md): vault skill log first,
Telegram second when notifications.telegram_chat_id is set.
Config: [agent_folder]/digest.md
The digest spec is a vault note the user can edit in Obsidian — never hard-code sections or symbols in this skill. Format:
---
tags: [agent-config, digest]
---
# Digest Config
## Markets
- gold, oil (WTI/Brent)
- SET index
- USD/THB
- BTC (THB)
## News
- AI / LLM
- Dev / Open Source
- ธุรกิจเทคโลก
- ข่าวไทย (เศรษฐกิจ/เทค)
## Reddit
- r/LocalLLaMA
- r/ClaudeAI
- r/selfhosted
## X
- best-effort: AI trends
Section headings are the contract: a missing heading = section off. An empty ## X
section or a missing one = skip X entirely.
Step 0: Config resolution
- Read
[agent_folder]/digest.md. - Found → proceed to Step 1.
- Missing + interactive session → run the Interview (below), generate the config note from the answers, confirm, then proceed.
- Missing + headless (
headless: true) → write a one-line skill-log entry "digest config missing — run /digest interactively once to set up" and stop. Never invent sections for a user who has not chosen them.
Interview (first run, interactive only)
Ask with AskUserQuestion (multiSelect where sensible), one question per group:
- Markets — which of: gold+oil · local stock index · local currency vs USD · BTC/crypto
- News topics — free set; offer AI/LLM, dev/open-source, global tech business, local news as starters
- Reddit subs — offer 3–4 relevant subs based on what you know of the user; accept custom
- X section — include (best-effort, explain the quality limit: no API, only what search surfaces) or skip
Write [agent_folder]/digest.md from the answers using the format above, show the
user the note path, and remind them it is theirs to edit.
- Schedule offer (last interview question): "ให้รันอัตโนมัติทุกเช้ามั้ย? กี่โมง?"
(default 08:30). On yes: append the entry to
onebrain.yml'sschedule:block — match the file's existing list style exactly — and runonebrain schedule register; confirm with the ✓/✗ state fromonebrain schedule list. On skip: mention/schedule-addworks any time later. Never re-offer when a/digestentry already exists in the schedule block. - Telegram offer (only when it can work): if the telegram channel tools are
available in this session AND
notifications.telegram_chat_idis not set, run the Notification Offer flow fromschedule-add/SKILL.md— user sends the bot one message, the incoming channel tag carrieschat_id, write it toonebrain.ymland confirm with a test send. If the telegram tools are absent, say nothing about Telegram (vault-log delivery is the normal path). This makes the first/digestconversation a complete setup: sections → schedule → delivery channel, no second command required.
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.
- 4d ago First seen · 154 lines · 101 tokens per session scan A 5f4ae7e2d2bd
digest is a skill published in the GitHub repository onebrain-ai/onebrain (25 stars, last pushed 6d ago), licensed Apache-2.0. It adds 101 tokens to every session and 1,749 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
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.
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…
paper-glossary
Use when building reusable Obsidian glossary notes from an existing paper source manifest, optionally with a raw-sections override, especially when a reader needs a reviewed shortlist before glossary notes and article links are changed.
youtube-fetcher
Turn a YouTube video into a structured, Obsidian-ready archival Markdown note containing its transcript, creator metadata, description, chapters, language, and capture provenance. Use when a user shares a YouTube URL or video ID and wants transcripts, captions, subtitles, notes, a knowledge-base record, summarization…
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-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.