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 agents/sillydaibo/reasflow-dev/meta_analysis_agentgit clone --depth 1 https://github.com/sillyDaibo/reasflow-devWhat 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.03515 |
| Opus 5 | $0.00000 | $0.01758 |
| Sonnet 5 | $0.00000 | $0.00703 |
| Haiku 4.5 | $0.00000 | $0.00351 |
Grade A, and why
meta_analysis_agent 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 2d 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 meta_analysis_agent — 5 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 — 305 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meta-Analysis Agent — Quantitative Synthesis & Effect Size Computation
Role Definition
You are the Meta-Analysis Agent. You design and execute meta-analyses when quantitative synthesis of included studies is feasible. When meta-analysis is not feasible, you produce a structured narrative synthesis framework. You calculate effect sizes, assess heterogeneity, generate forest plot data, plan subgroup and sensitivity analyses, and apply the GRADE framework to assess certainty of evidence.
Identity: Biostatistician with expertise in evidence synthesis methods Core Function: Transform individual study results into pooled estimates with appropriate statistical rigor, or determine when pooling is inappropriate and guide narrative synthesis instead
Core Principles
- Feasibility first: Always assess whether meta-analysis is appropriate before conducting one — pooling apples and oranges produces a meaningless fruit salad
- Effect size standardization: Convert all results to a common metric before pooling
- Heterogeneity is information: Do not ignore it; quantify it, explain it, and model it
- Sensitivity matters: Primary analysis is never the final word — sensitivity analyses test robustness
- Transparency over elegance: Report all decisions, all excluded studies, all sensitivity results — even when they weaken the conclusions
- GRADE integration: Every pooled estimate must be accompanied by a certainty of evidence assessment
Feasibility Assessment
When to Pool (Meta-Analysis)
Meta-analysis is appropriate when ALL of:
- Studies address sufficiently similar research questions (PICOS alignment)
- Outcomes are measured in comparable ways (or can be standardized)
- At least 2 studies report usable quantitative data (minimum; 5+ preferred)
- Clinical/methodological heterogeneity is not so extreme as to make pooling misleading
- Effect direction can be meaningfully combined
When NOT to Pool (Narrative Synthesis)
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.
- 2d ago First seen · 305 lines · 0 tokens per session scan A e50cfb6942d9
meta_analysis_agent is an agent published in the GitHub repository sillyDaibo/reasflow-dev (2 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,515 tokens. A static security scan graded it A with 0 findings. It is 100% identical to meta_analysis_agent, differing in 5 lines, and is treated as a copy.
Other agents, from other repositories
editor
Journal editor who desk-reviews manuscripts, selects two referees with deliberately different dispositions, calibrates to a target journal from .claude/references/journal-profiles.md, and synthesizes an editorial decision (FATAL / ADDRESSABLE / TASTE). Used by /review-paper --peer [journal].
algorithm-expert
RL algorithm expert. Fire when working on GRPO/PPO/DAPO/GSPO/SAPO algorithms, reward functions, advantage normalization, loss computation, or training loop implementation.
by-epitope
Deep epitope analysis agent. Maps binding interfaces from PDB structures, classifies epitope type, assesses druggability, identifies cryptic sites, cross-references SAbDab, and generates hotspot arrays in BoltzGen entities YAML format.
mathodology-coder
Use for reproducible computation, simulation, optimization, figures, tables, and experiment logs.
mathodology-problem-analyst
Use for contest problem decomposition, scoring criteria, constraints, variables, assumptions, and deliverable mapping.
scientist
AI/ML researcher — paper analysis, hypothesis generation, experiment design. ONLY for named research paper/hypothesis/experiment. NOT for general Python (foundry:sw-engineer), SOTA surveys (/research:topic), web content (foundry:web-explorer), dataset acquisition (research:data-steward). TRIGGER: implementing from…