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 cynthiajones34/GBrain --skill gbrain-advisorgit clone --depth 1 https://github.com/cynthiajones34/GBrainWrote 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/cynthiajones34/gbrain/gbrain-advisor)<a href="https://agentmods.dev/skills/cynthiajones34/gbrain/gbrain-advisor"><img src="https://agentmods.dev/badge/skills/cynthiajones34/gbrain/gbrain-advisor/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/cynthiajones34/gbrain/gbrain-advisor"><img src="https://agentmods.dev/badge/skills/cynthiajones34/gbrain/gbrain-advisor.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00076 | $0.01159 |
| Opus 5 | $0.00038 | $0.00580 |
| Sonnet 5 | $0.00015 | $0.00232 |
| Haiku 4.5 | $0.00008 | $0.00116 |
Grade A, and why
gbrain-advisor 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 9d 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.
This is a copy
95% identical to gbrain-advisor — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gbrain Advisor
Convention: See
skills/conventions/brain-first.md. This skill is the proactive voice of the brain — it tells the owner how to run it better.
Contract
This skill guarantees:
- Read-only.
gbrain advisornever mutates. It computes a ranked list of actions from existing brain state. - Print, never execute. You SHOW the user the findings and ASK before running any fix. The user owns every decision.
- Bounded nagging. On a cadence, surface only what changed or what's critical; don't repeat an ignored low-severity item every run.
When to run
- On demand when the user asks "how do I get more out of this brain?"
- On a weekly cadence via the cron recipe below (even idle brains get a "here's how to run this better" ping).
How to run it
gbrain advisor --json
Exit code is the severity gate (E2): 0 clean, 1 warn, 2 critical. The JSON
payload is { version, generated_at, worst, findings: [...] }. Each finding has:
severity—critical|warn|infotitle— one-line why-it-mattersfix.command_argv— the exact command to fix it (a structured argv)fix.dispatch_id— present when the fix is safe to run via--apply
What to do with the findings
-
Read the findings, highest severity first.
-
Summarize the top 1-3 to the user in their own channel/voice. Lead with any
criticalitem (e.g. pending migrations). -
For each, show the
fix.command_argvand ask whether to run it. -
If they say yes and the finding has a
fix.dispatch_id, you may run it locally with an explicit confirm:gbrain advisor --apply <dispatch_id>--applyis local-only, runs the fix as a structured argv (no shell), and confirms first. Findings without adispatch_idare not auto-runnable — run theirfix.command_argvyourself after the user agrees. -
Never run a fix the user didn't approve.
Cron recipe (weekly checkup)
Install a weekly job via the cron-scheduler skill. Keep the prompt THIN — the
job just reads this skill and runs the advisor:
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.
- 9d ago First seen · 118 lines · 76 tokens per session scan A c15c7a88bee2
gbrain-advisor is a skill published in the GitHub repository cynthiajones34/GBrain (0 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session and 1,159 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to gbrain-advisor, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
potpie-source-ingestion
Use when the user explicitly asks to ingest, refresh, or deeply understand a repository, PR, issue, ticket, runbook, incident report, document, or web link into Potpie. The harness performs todo-driven discovery, uses local/GitHub/integration tools and read-only subagents when available, builds evidence-backed…
backfill-enumerate-drain
How to backfill a newly-added repo or team — the enumerate-then-drain loop, the single-event contract, and resume-safe todo discipline. Load this when handling a .added seed event with the planner on.
knowledge-base-management
A lifecycle system for managing an Obsidian knowledge base, which is a folder of linked notes. It organizes raw material, AI-maintained wiki pages, and generated views into separate layers.
memora
Use when working with persistent memory across sessions, storing/retrieving knowledge, managing TODOs/issues, or when context from previous sessions would be helpful.
daily-journal
A passive daily work journal that Claude keeps FOR you so you never have to write it yourself. Append short entries after meaningful work (what was done, what you focused on, artifacts touched) to 01-daily/journal/YYYY-MM-DD.md. Run a guided reflection at night or in the morning. Use when you run /daily-journal, say…
meeting-transcript
Process meeting recordings and notes into structured decisions, action items, and team dynamics with intelligent noise filtering.