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 meeting-ingestiongit 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/meeting-ingestion)<a href="https://agentmods.dev/skills/cynthiajones34/gbrain/meeting-ingestion"><img src="https://agentmods.dev/badge/skills/cynthiajones34/gbrain/meeting-ingestion/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/meeting-ingestion"><img src="https://agentmods.dev/badge/skills/cynthiajones34/gbrain/meeting-ingestion.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.00042 | $0.00843 |
| Opus 5 | $0.00021 | $0.00421 |
| Sonnet 5 | $0.00008 | $0.00169 |
| Haiku 4.5 | $0.00004 | $0.00084 |
Grade A, and why
meeting-ingestion 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 11d 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 meeting-ingestion — 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meeting Ingestion Skill
Filing rule: Read
skills/_brain-filing-rules.mdbefore creating any new page.
Contract
This skill guarantees:
- Meeting page created with attendees, summary, key decisions, action items
- EVERY attendee gets a people page (created or updated)
- EVERY company discussed gets entity propagation
- Timeline entries on ALL mentioned entities (timeline merge)
- Meeting is NOT fully ingested until enrich runs for every entity
- Back-links created bidirectionally
Convention: See
skills/conventions/quality.mdfor Iron Law back-linking.
Every attendee and company mentioned MUST get a back-link from their page to the meeting page. An unlinked mention is a broken brain.
Phases
Phase 1: Parse the transcript
Extract from the transcript:
- Attendees (names, roles if available)
- Date, time, duration
- Key topics discussed
- Decisions made
- Action items with owners
- Companies and projects mentioned
Phase 2: Create meeting page
# {Meeting Title} — {Date}
**Attendees:** {list with links to people pages}
**Date:** {YYYY-MM-DD}
**Duration:** {if available}
## Summary
{3-5 bullet key outcomes}
## Key Decisions
{Decisions with context}
## Action Items
{Tasks with owners and deadlines}
## Discussion Notes
{Structured notes by topic}
Phase 3: Attendee enrichment (MANDATORY)
For EACH attendee:
gbrain search "{name}"— does a people page exist?- If NO → create via enrich skill (this is mandatory, not optional)
- If YES → update compiled truth with meeting context
- Add timeline entry on the person's page:
gbrain timeline-add <person-slug> <date> "Attended <meeting-title>"
Note (v0.10.1): Once the meeting page is written via gbrain put, the
auto-link post-hook automatically creates attended links from the meeting
to each attendee whose page is referenced as [Name](people/slug). You don't
need to call gbrain link for attendees. You DO still need gbrain timeline-add
for dated events (auto-link only handles links, not timeline entries).
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.
- 11d ago First seen · 125 lines · 42 tokens per session scan A 7767334c63ff
meeting-ingestion is a skill published in the GitHub repository cynthiajones34/GBrain (0 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 843 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to meeting-ingestion, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
memory-proactive
Proactive layered recall and generic domain-aware routing.
memory-archivist
A set of scripts for archiving conversations, syncing them to a knowledge graph, updating summaries, and managing stored memories over time. A knowledge graph is a linked collection of information and relationships.
memory-starter-kit
Historical starter note for the memory sidecar stack.
mind
Local project memory with recall, provenance, policy, and dreams.
personal-knowledge-graph
Use when maintaining a LoomKG/Obsidian knowledge graph.
shodh-memory
Persistent memory system for AI agents. Use this skill to remember context across conversations, recall relevant information, and build long-term knowledge. Activate when you need to store decisions, learnings, errors, or context that should persist beyond the current session.