GBrain is a memory and retrieval layer for AI agents that searches, connects, and synthesizes information from stored sources. It is used to give coding agents and autonomous agents access to knowledge beyond their current code, including shared company information with access controls. The catalogue add-ons help agents operate GBrain and connect it to agent workflows.
Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/garrytan/gbrainnpx agentmods add skills/garrytan/gbrain/academic-verifyWrote 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/garrytan/gbrain/academic-verify)<a href="https://agentmods.dev/skills/garrytan/gbrain/academic-verify"><img src="https://agentmods.dev/badge/skills/garrytan/gbrain/academic-verify.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.1 | $0.00074 | $0.02164 |
| Opus 5 | $0.00037 | $0.01082 |
| Sonnet 5 | $0.00015 | $0.00433 |
| Haiku 4.5 | $0.00007 | $0.00216 |
Grade A, and why
academic-verify 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 7d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- academic-verify — 100% identical, 0 lines differ
- academic-verify — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
academic-verify — Trace Claims to Source Data
Convention: see conventions/quality.md for citation rules; every verdict cites the source data, not just the author's claim about the source data.
Convention: see conventions/brain-first.md for the lookup chain. This skill enforces brain-first by checking existing brain pages before issuing a fresh web search.
What this is
A claim-verification flow for academic / research statements. When a book, article, or speaker cites a study or quotes a number, this skill traces the claim through:
claim → publication → methodology section → raw data source → independent verification
At each step, it answers:
- Where does this number come from? (Self-generated? Survey? Government data?)
- What's the baseline? (Reduction from what? Over what time period?)
- Is the raw data available? (Public? Proprietary? "Available on request"?)
- Has anyone independently verified it? (Replication study? Government audit?)
- Are there confounding factors? (Other interventions, policy changes, COVID, sampling bias?)
- Is the comparison fair? (Cherry-picked comparison group? Survivorship bias?)
The output is a brain page under concepts/<claim-slug>.md that records
the claim, the trace, and the verdict — so future references to the
same claim can re-use the verified analysis.
When to use this
- A book quotes a study and you want to confirm it's real and not miscited
- An article makes a quantified claim ("X reduced Y by 40%") that you want traced to the source data
- You're writing something that depends on a piece of research and you want to verify the underlying paper holds up
- You're updating a brain page that cites a research claim and you want to record the verification status alongside
What this skill is NOT
- Not adversarial / oppo work. The point is rigor, not takedown.
- Not generic web research — use
perplexity-researchdirectly for open-ended topic exploration. - Not a brain-only lookup — that's
gbrain query.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 226 lines · 74 tokens per session scan A 1c19e27e7524
academic-verify is a skill published in the GitHub repository garrytan/gbrain (29,629 stars, last pushed 3d ago), licensed MIT. It adds 74 tokens to every session and 2,164 once invoked, about $0.0004 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-30.
Other skills, from other repositories
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…