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 smixs/agent-second-brain --skill dbrain-processorgit clone --depth 1 https://github.com/smixs/agent-second-brainWrote 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/smixs/agent-second-brain/dbrain-processor)<a href="https://agentmods.dev/skills/smixs/agent-second-brain/dbrain-processor"><img src="https://agentmods.dev/badge/skills/smixs/agent-second-brain/dbrain-processor/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/smixs/agent-second-brain/dbrain-processor"><img src="https://agentmods.dev/badge/skills/smixs/agent-second-brain/dbrain-processor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium analysis-evasion · line 1 Suspicious Unicode normalization or mixed-script contentFix: Review the flagged content for security risks. Ensure no credentials, secrets, or sensitive data are exposed.
- medium Rogue Agent · line 363 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Agent Snooping · line 510 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00060 | $0.03954 |
| Opus 5.5 | $0.00024 | $0.01582 |
| Sonnet 5.5 | $0.00012 | $0.00791 |
| Haiku 4.5 | $0.00006 | $0.00395 |
Grade A, and why
dbrain-processor 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 1mo 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 — 513 lines — stays where its author put it; the contents beside it link to each section on GitHub.
d-brain Processor
Process daily entries → thoughts (Obsidian) + HTML report (Telegram).
Integrates with Your Business data for business context.
CRITICAL: Output Format
ALWAYS return RAW HTML. No exceptions. No markdown. Ever.
Your final output goes directly to Telegram with parse_mode=HTML.
Rules:
- ALWAYS return HTML report — even if entries already processed
- ALWAYS use the template below — no free-form text
- NEVER use markdown syntax (**, ##, ```, -)
- NEVER explain what you did in plain text — put it in HTML report
WRONG:
<b>Title</b>
CORRECT: Title
Processing Flow
- Load personal context — Read goals/1-yearly, goals/2-monthly, goals/3-weekly
- Load business context:
- Read
business/_index.md— Your Business (клиенты, проекты, CRM) - Read
projects/_index.md— личные проекты (если релевантно)
- Read
- Read daily — daily/YYYY-MM-DD.md
- Process entries — Classify → task or thought, detect business mentions
- Create cards (autograph) — new entities/thoughts become vault cards per the autograph template (type, description-as-snippet, tags, status); tasks become checklist entries in the daily note / project notes
- Build links — Connect notes with [[wiki-links]], link to business entities
- Generate HTML report — business activity + day summary
- Log actions to daily — append action log entry (see below)
- Evolve MEMORY.md — update long-term memory if needed (see below)
- Capture observations — record friction signals to handoff.md (see below)
ОБЯЗАТЕЛЬНО: Логирование в daily/
После ЛЮБЫХ изменений в vault — СРАЗУ пиши в daily/YYYY-MM-DD.md:
Формат:
## HH:MM [text]
{Описание действий}
**Создано/Обновлено:**
- [[path/to/file|Name]] — описание
Что логировать:
- Создание файлов в thoughts/
- Обновление business/ или projects/
- Добавление task-записей в daily/проекты
- Синхронизация с внешними системами
Пример:
## 14:30 [text]
Обработка ежедневных записей
**Создано задач:** 2
- [ ] Follow-up Acme Corp (due: завтра, p2)
- [ ] Подготовить КП Unilever (due: пятница, p2)
**Сохранено мыслей:** 1
- [[thoughts/ideas/product-launch|Product Launch]] — идея запуска
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- phases/capture.md 3.0 KB
- phases/execute.md 2.0 KB
- phases/reflect.md 2.2 KB
- references/about.md 544 B
- references/business-context.md 642 B
- references/classification.md 6.2 KB
- references/contacts.md 298 B
- references/goals.md 2.8 KB
- references/links.md 5.0 KB
- references/report-template.md 3.4 KB
- references/rules.md 2.1 KB
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.
- 1mo ago First seen · 513 lines · 60 tokens per session scan A fca129032676
dbrain-processor is a skill published in the GitHub repository smixs/agent-second-brain (403 stars, last pushed 2mo ago), licensed MIT. It adds 60 tokens to every session and 3,954 once invoked, about $0.0002 per session on Opus 5.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
computer-history
Answer questions about what the user recently did on their computer — who contacted them, what they were working on, where they left off — by reading the local Computer History summaries and raw event streams.
context-preservation
State capture and restore across context window compactions. Monitors usage thresholds and serializes quality, task, and spec state for seamless continuation.
wisdom-forget
Remove a must-keep CocoWisdom entry with rationale. Usage: $wisdom forget --id --rationale " ".
memora
Use when working with persistent memory across sessions, storing/retrieving knowledge, managing TODOs/issues, or when context from previous sessions would be helpful.
telegram-userbot
A skill for connecting to and working through the owner's personal Telegram account, rather than a Telegram bot. It can read personal chats, search messages, and send messages as the account owner after setup and consent.
ori-memory
Persistent agent memory with learning retrieval. Knowledge graph on markdown files — capture insights, decisions, research, and learnings during work, then retrieve them weeks or months later. Use when knowledge is too valuable to lose but too much to inject into every prompt.