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/humanerd-drew/opencode-drewgent/brain-dashboard-systemnpx skills add humanerd-drew/opencode-drewgent --skill brain-dashboard-systemgit clone --depth 1 https://github.com/humanerd-drew/opencode-drewgentWrote 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/humanerd-drew/opencode-drewgent/brain-dashboard-system)<a href="https://agentmods.dev/skills/humanerd-drew/opencode-drewgent/brain-dashboard-system"><img src="https://agentmods.dev/badge/skills/humanerd-drew/opencode-drewgent/brain-dashboard-system.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.00000 | $0.01422 |
| Opus 5 | $0.00000 | $0.00711 |
| Sonnet 5 | $0.00000 | $0.00284 |
| Haiku 4.5 | $0.00000 | $0.00142 |
Grade A, and why
brain-dashboard-system 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
space: outcome type: document
Brain Dashboard System
{{AGENT_NAME}}의 NeuronFS Brain 상태를 실시간으로 모니터링하는 통합 시스템.
아키텍처
┌─────────────────────────────────────────────────────┐
│ {{AGENT_NAME}} Brain │
│ │
│ ┌─────────────┐ ┌──────────────────────────────┐ │
│ │ Brain Rules │ │ Scripts (~/.{{AGENT_NAME_LOWER}}/scripts) │ │
│ │ .neuron │──│ brain_nodes.py (ASCII 뇌) │ │
│ │ files │ │ brain_html_dashboard.py (WEB) │ │
│ └─────────────┘ │ brain_rule_monitor.py │ │
│ │ session_end_hook.py │ │
│ └──────────────────────────────┘ │
│ │ │
│ ┌────────────────────┼────────────┐ │
│ ▼ ▼ ▼ │
│ ┌────────────┐ ┌──────────────┐ ┌───────────┐ │
│ │ Cron 6h │ │ Cron 5min │ │ Discord │ │
│ │ Growth Rep │ │ Session End │ │ Alert │ │
│ └────────────┘ └──────────────┘ └───────────┘ │
└─────────────────────────────────────────────────────┘
핵심 스크립트
1. brain_nodes.py (ASCII 뇌 시각화)
python3 ~/.{{AGENT_NAME_LOWER}}/scripts/brain_nodes.py
실제 뇌 해부학 구조를 반영한 ASCII 아트:
- P6 Prefrontal (맨 위/앞) → P0 Brainstem (맨 아래)
- Synapse Signal Flow: P0→P1→P2→P3→P4→P5→P6
- Spinal Cord 포함
- Stats + Growth delta 표시
2. brain_html_dashboard.py (웹 대시보드)
python3 ~/.{{AGENT_NAME_LOWER}}/scripts/brain_html_dashboard.py
출력: ~/.{{AGENT_NAME_LOWER}}/brain_dashboard.html
- SVG 뇌 시각화 (애니메이션 시냅스 신호)
- Stats 카드 4개 (Brain Rules, Skills, Knowledge, Sessions)
- Layer Detail 테이블
- Skills 라이브러리
- 5분 자동 리프레시
3. brain_rule_monitor.py (성장 모니터)
python3 ~/.{{AGENT_NAME_LOWER}}/scripts/brain_rule_monitor.py # 실행
python3 ~/.{{AGENT_NAME_LOWER}}/scripts/brain_rule_monitor.py --check # 상태 확인
- brain_rule_state.json 와 비교하여 신규 규칙 탐지
- 새 규칙 발견 시 Discord 알림 (webhook)
- Discord 설정:
~/.{{AGENT_NAME_LOWER}}/config/discord.json(webhook_url 필요)
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 · 141 lines · 0 tokens per session scan A 26c746c95a49
brain-dashboard-system is a skill published in the GitHub repository humanerd-drew/opencode-drewgent (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,422 tokens. 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…