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/hrithik-gavankar/brainstack/team-brainnpx skills add Hrithik-Gavankar/brainstack --skill team-braingit clone --depth 1 https://github.com/Hrithik-Gavankar/brainstackWrote 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/hrithik-gavankar/brainstack/team-brain)<a href="https://agentmods.dev/skills/hrithik-gavankar/brainstack/team-brain"><img src="https://agentmods.dev/badge/skills/hrithik-gavankar/brainstack/team-brain.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.00065 | $0.02404 |
| Opus 5 | $0.00032 | $0.01202 |
| Sonnet 5 | $0.00013 | $0.00481 |
| Haiku 4.5 | $0.00006 | $0.00240 |
Grade A, and why
team-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 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team Brain — Sync Mode
Part of Brainstack: personal=engineer-brain, crew=team-brain.
| Prefer | Fallback |
|---|---|
MCP start / prepare_research / recall / remember / compliance / peer_notify / correct / history / restore / touch |
bash …/team-brain-api.sh … |
Peer push (#31)
start may attach a Realtime signal listener (bodies still via authenticated pull).
If .team-brain/notify/<KEY>.json updates mid-session, summarize new peer memories before continuing.
If push is unavailable (TEAM_BRAIN_REALTIME=off / no websockets / migration missing), poll/watch/recall still work.
Repo pin (#39) + roles (#40)
- Prefer pinned Jira key from
.team-brain/project.jsonwhen the user omits a key (start/attach). - Never put anon / api_key / invite into the pin — credentials stay gitignored.
whoami.role:viewer→ recall only;member/admin→ remember OK; onlyadminrotates invites.
Compliance (policy=stronger_prompts)
v1 follow-up chose stronger prompts + soft session gate (not a hard CLI block).
- Before deep research:
research_okmust be true (startloads context, orprepare_research/recall). - If
sync_status/compliancereturnsagent_action, follow it before coding. - After durable findings:
rememberwithsource_refin the same turn. - Humans may still use the CLI offline; agents must not skip the loop.
- Never upload personal
BRAIN.md.
bash "$API" compliance <JIRA-KEY>
bash "$API" sync-status <JIRA-KEY> # embeds compliance
API="${SKILL_DIR}/scripts/team-brain-api.sh"
# or: <engineer-brain-repo>/core/scripts/team-brain-api.sh
Product loop (what the engineer does)
- One manual step — start sync for the ticket
- Automatic while active — background pull into cache; you summarize + work
- Save findings —
rememberwithsource_ref(merge-safe) - On human correction —
correct(or re-remembersamesource_ref) + optionallearning - Long spikes — periodic
recall(or optional backgroundwatch); do not spam every turn - Idle sleep — after ~1h no activity, sync sleeps; prompt user to
wake
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 · 243 lines · 65 tokens per session scan A d27a49867f52
team-brain is a skill published in the GitHub repository Hrithik-Gavankar/brainstack (5 stars, last pushed 14d ago), licensed MIT. It adds 65 tokens to every session and 2,404 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-31.
Other skills, from other repositories
init-workspace-documentation
Skill "init-workspace-documentation" from griddynamics/rosetta, covering agent memory.md, agent memory, preventive rules, what worked and what failed.
context-cycle-proactive
At 80-90% context, save to the brain, route to the right channel, load fresh context, and resume. Built-in lifecycle so every agent stays synced to the second brain and never drops work.
kb-memory
Use when knowledge base and memory system for AI agents. Covers company KB, persistent memory, session recall, and brain architecture for context preservation.
context-agent
Agente de contexto para continuidade entre sessoes. Salva resumos, decisoes, tarefas pendentes e carrega briefing automatico na sessao seguinte.
llm-wiki
The foundational knowledge distillation pattern for building and maintaining an AI-powered Obsidian wiki. Based on Andrej Karpathy's LLM Wiki architecture. Use this skill whenever the user wants to understand the wiki pattern, set up a new knowledge base, or needs guidance on the three-layer architecture (raw sources…
wiki-lint
Audit and maintain the health of the Obsidian wiki. Use this skill when the user wants to check their wiki for issues, find orphaned pages, detect contradictions, identify stale content, fix broken wikilinks, or perform general maintenance on their knowledge base. Also triggers on "clean up the wiki", "what needs…