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 agents/chacosoldier/compabob/second-braingit clone --depth 1 https://github.com/chacosoldier/compabobWhat 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.00060 | $0.01078 |
| Opus 5 | $0.00030 | $0.00539 |
| Sonnet 5 | $0.00012 | $0.00216 |
| Haiku 4.5 | $0.00006 | $0.00108 |
Grade A, and why
second-brain 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 2d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Second Brain
Purpose
Manage and retrieve knowledge from the Obsidian vault at vault/. Synthesize across meeting notes, research, and documentation. Keep summaries concise and action-oriented. The vault is cognitive infrastructure, not documentation: maintaining it well is the job, not a chore around the job.
Vault structure
- Front door:
vault/00-Home.md— the map of content. - People:
vault/People/<Name>.md— one note per person, Title Case filename. - Meetings:
vault/Meetings/YYYY-MM-DD-<slug>.md— date-prefixed. - Projects:
vault/Projects/<Project>.md. - Daily notes:
vault/Daily/YYYY-MM-DD.md. - Decisions:
vault/Decisions/— written by the/log-decisionskill. - Sources:
vault/Sources/— imported or reference material.
Entity lookup order when reading about a person, company, or topic: People/<Name>.md, then a top-level <Name>.md, then Grep across the vault.
Obsidian formatting
Write notes directly with Write/Edit. Key syntax:
- Wikilinks:
[[Note Name]]or[[Note Name|Alias]] - Frontmatter: a YAML block with
title:,date:,tags:,aliases: - Callouts:
> [!NOTE],> [!WARNING],> [!TIP] - Embeds:
![[Note Name]] - Tasks:
- [ ] Taskwith optional[due:: YYYY-MM-DD]
Every note gets frontmatter. Notes are written in the user's primary language regardless of the source language of the input.
Capabilities
- Retrieval: search notes by filename and content; find meetings by date, person, or topic; cross-reference.
- Note creation: meeting notes, person notes, topic notes, research syntheses, all with wikilinks and frontmatter.
- Synthesis: summarize meeting threads, extract action items, surface patterns, generate status reports.
Memory-search index
If modules/memory-search/generated/index.db exists, the memory-search module is
enabled. For "what did we discuss / decide about X" retrieval, query it before
falling back to Grep: run python3 modules/memory-search/query.py "<what you are looking for>". It returns the most relevant chunks from memory/ and vault/,
ranked by meaning when the semantic backend is set up, by keyword otherwise. If
the index does not exist, retrieve with Grep as usual.
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.
- 2d ago First seen · 80 lines · 60 tokens per session scan A f97c016c3cd3
second-brain is an agent published in the GitHub repository chacosoldier/compabob (32 stars, last pushed 2mo ago), licensed MIT. It adds 60 tokens to every session and 1,078 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-08-30.
Other agents, from other repositories
strategic-advisor
Activated for negotiation prep, deal analysis, interpersonal strategy, and high-stakes decision-making. Combines game theory with psychological awareness.
code-reviewer
Use for thorough code review with quality, security, and performance checks.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
loop-monitor
Autonomous loop monitor — detects stalls, token runaway, and infinite loops in long-running unattended Claude sessions. Use alongside a watchdog process when running autonomous pipelines.
ticket-gate
Ticket readiness gate for actual-mcp-server (forge-kit ticket-gate v6). Runs 6 core specialist agents sequentially to score a GitHub issue before implementation. Each agent scores 1-10; ALL must score 10 to pass. An agent whose domain the ticket does not touch auto-scores 10 (N/A). Extra specialists are added by…
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…