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 briefinggit 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/briefing)<a href="https://agentmods.dev/skills/cynthiajones34/gbrain/briefing"><img src="https://agentmods.dev/badge/skills/cynthiajones34/gbrain/briefing/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/briefing"><img src="https://agentmods.dev/badge/skills/cynthiajones34/gbrain/briefing.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.00016 | $0.01464 |
| Opus 5 | $0.00008 | $0.00732 |
| Sonnet 5 | $0.00003 | $0.00293 |
| Haiku 4.5 | $0.00002 | $0.00146 |
Grade A, and why
briefing 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 8d 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
100% identical to briefing — 0 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Briefing Skill
Compile a daily briefing from brain context.
Filing rule: When the briefing creates or updates brain pages, follow
skills/_brain-filing-rules.md.
Contract
- Every fact in the briefing includes an inline
[Source: slug, updated DATE]citation. - Meeting participants are resolved against the brain; gaps are explicitly flagged.
- Active deals and action items include deadlines and recency context.
- The briefing is read-only: no brain pages are created or modified unless the user explicitly requests it.
- Stale alerts surface pages relevant to today's context, not just all stale pages.
Phases
-
Hot memory pulse (v0.32). Before composing anything else, run:
gbrain recall --since-last-run --supersessions --pending --rollup --jsonFold the result into the briefing under a "Brain pulse" section at the top:
- Contradictions resolved overnight — the
--supersessionsoutput. Lead with these because they're new corrections to your model of the world. - Top mentions —
top_entitiesfrom--rollup(top 5 entity slugs by fact count in the window). - New facts since last briefing — group the
factsarray under each entity from the rollup; includekind,notability, andconfidence. - Pending consolidation footer — when
pending_consolidation_count > 0, noteN facts await dream-cycle consolidationso the operator can decide whether to rungbrain dreambefore reading further.
The
--since-last-runflag advances~/.gbrain/recall-cursors/<source>.jsonso the next briefing picks up exactly where this one left off. If you're running this as a cron job, pass--source <slug>or setGBRAIN_SOURCEexplicitly — cron doesn't start in your repo-root cwd, so dotfile resolution may miss the right source. Thin-client installs (gbrain init --mcp-only) route through the remote brain transparently. - Contradictions resolved overnight — the
-
Today's meetings. For each meeting on the calendar:
- Search gbrain for each participant by name
- Read their pages from gbrain for compiled_truth context
- Summarize: who they are, recent timeline, relationship to you
-
Active deals. List deal pages in gbrain filtered to active status:
- Deadlines approaching in the next 7 days
- Recent timeline entries (last 7 days)
-
Time-sensitive threads. Open items from timeline entries:
- Items with deadlines in the next 48 hours
- Follow-ups that are overdue
-
Recent changes. Pages updated in the last 24 hours:
- What changed and why (read timeline entries from gbrain)
-
People in play. List person pages in gbrain sorted by recency:
- Updated in last 7 days
- Have high activity (many recent timeline entries)
-
Stale alerts. From gbrain health check:
- Pages flagged as stale that are relevant to today's meetings
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.
- 8d ago First seen · 153 lines · 16 tokens per session scan A a661804c3eb2
briefing is a skill published in the GitHub repository cynthiajones34/GBrain (0 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 1,464 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to briefing, differing in 0 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.