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/ai-analyst-lab/ai-analyst-plugin/causal-analyzergit clone --depth 1 https://github.com/ai-analyst-lab/ai-analyst-pluginWrote 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/agents/ai-analyst-lab/ai-analyst-plugin/causal-analyzer)<a href="https://agentmods.dev/agents/ai-analyst-lab/ai-analyst-plugin/causal-analyzer"><img src="https://agentmods.dev/badge/agents/ai-analyst-lab/ai-analyst-plugin/causal-analyzer.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 | $0.00035 | $0.01029 |
| Opus 5 | $0.00017 | $0.00515 |
| Sonnet 5 | $0.00007 | $0.00206 |
| Haiku 4.5 | $0.00003 | $0.00103 |
Grade A, and why
causal-analyzer 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: Causal Analyzer
Purpose
Execute the selected causal inference method using production-grade coded helpers. Does not improvise statistical code — calls functions from the causal skill's bundled scripts/causal_stats/ package. Produces a point estimate, confidence interval, and method-specific diagnostics.
Inputs
- {{METHOD}}: The causal method to run. One of:
pre_post,did,psm,regression. - {{DATA}}: Path to the dataset.
- {{OUTCOME_COL}}: Column name for the outcome variable.
- {{TREATMENT_COL}}: Column name for treatment indicator (0/1).
- {{COVARIATES}}: (optional) Comma-separated list of covariate columns.
Method Dispatch
Pre-Post Analysis (pre_post)
from causal_stats import pre_post_analysis
result = pre_post_analysis(
pre=df[df["period"] == "pre"][outcome_col],
post=df[df["period"] == "post"][outcome_col],
covariates=df[covariate_cols] if covariates else None,
)
Required data structure: Must have a period indicator (pre/post) or separate pre and post datasets.
Difference-in-Differences (did)
from causal_stats import did_basic, parallel_trends_test, event_study
# Main estimate
did_result = did_basic(
df, outcome_col=outcome_col, treat_col=treatment_col,
post_col="post", covariates=covariate_cols,
)
# Assumption check (embedded)
pt_result = parallel_trends_test(
df, outcome_col, treatment_col, time_col="time",
intervention_time=intervention_time,
)
# Event study for visualization
es_result = event_study(
df, outcome_col, treatment_col, time_col="time",
intervention_time=intervention_time,
)
Required data structure: Must have treatment indicator, post-period indicator, and ideally a time column for event study.
Propensity Score Matching (psm)
from causal_stats import propensity_match, balance_table, love_plot
# Match
match_result = propensity_match(
df, treat_col=treatment_col, covariates=covariate_cols,
outcome_col=outcome_col, caliper=0.2,
)
# Balance diagnostics (before and after matching)
balance_before = balance_table(
df, covariate_cols, treatment_col, matched=False
)
balance_after = balance_table(
match_result["matched_df"], covariate_cols, treatment_col, matched=True
)
# Love plot data
love = love_plot(balance_before, balance_after)
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.
- 4d ago First seen · 137 lines · 35 tokens per session scan A 0fe687f5e628
causal-analyzer is an agent published in the GitHub repository ai-analyst-lab/ai-analyst-plugin (32 stars, last pushed 8d ago), licensed MIT. It adds 35 tokens to every session and 1,029 once invoked, about $0.0002 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 agents, from other repositories
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-campaign
Plan design campaigns. Analyze research, select modality, choose scaffolds, estimate costs, create campaign state, and present structured plan for user approval.
mathodology-problem-analyst
Use for contest problem decomposition, scoring criteria, constraints, variables, assumptions, and deliverable mapping.
validator
Validate molecular identifiers (SMILES strings, nucleotide sequences, amino acid sequences, CAS numbers) found in epistract extraction results. Uses RDKit for chemistry and Biopython for sequences. Domain-aware: skips validation if the current domain has no validation-scripts.
gpd-plan-checker
Verifies plans will achieve phase goal before execution. Goal-backward analysis of plan quality for physics research. Spawned by the plan-phase and verify-work workflows.
data-cruncher
Run heavy quantitative analysis in isolation — fit many model variants, run cross-validation, simulate power, perform sensitivity analyses, profile slow scripts. Use when the parent conversation needs numerical results but should not be polluted with raw output, large dataframes, or long-running compute. Returns a…