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 vasilyu1983/AI-Agents-public --skill foundations-causal-inferencegit clone --depth 1 https://github.com/vasilyu1983/AI-Agents-publicWrote 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/vasilyu1983/ai-agents-public/foundations-causal-inference)<a href="https://agentmods.dev/skills/vasilyu1983/ai-agents-public/foundations-causal-inference"><img src="https://agentmods.dev/badge/skills/vasilyu1983/ai-agents-public/foundations-causal-inference/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/vasilyu1983/ai-agents-public/foundations-causal-inference"><img src="https://agentmods.dev/badge/skills/vasilyu1983/ai-agents-public/foundations-causal-inference.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00051 | $0.08364 |
| Opus 5 | $0.00026 | $0.04182 |
| Sonnet 5 | $0.00010 | $0.01673 |
| Haiku 4.5 | $0.00005 | $0.00836 |
Grade A, and why
foundations-causal-inference 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 9d 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 — 360 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Causal Inference Foundations
12 applied causal inference primitives for impact attribution and experiment design, backed by a formal theory map. Each primitive solves a specific identification or estimation problem. Primitives are domain-agnostic: the same instrumental-variable logic that handles omitted-variable bias in econometrics handles it in product analytics; the same difference-in-differences framework that evaluates policy interventions evaluates feature rollouts.
When to Apply
Apply causal-inference when:
- "Did the change cause the outcome, or just correlate?" question
- A/B test is impossible (rollout already happened, ethics, ramping risk) — observational methods needed
- Confounding suspected — non-random treatment assignment
- Heterogeneous treatment effects matter (CATE, uplift)
- Mediation question — "is the effect through path X or path Y?"
- Units interfere — marketplace, social graph, shared inventory, ranking model, or agents sharing a backend resource; randomization alone does not identify the launch effect
- LLM evaluation pipeline uses logged data — prompt distribution, judge bias, or user self-selection confound the quality signal (Pearl's Ladder applies: estimating P(Y|do(prompt)) is different from P(Y|prompt))
Skip and use simpler alternatives when:
- Clean RCT / A/B test is already running and units do not interfere — read the result, don't re-derive it observationally. If units share a marketplace, graph, or backend resource, the test is not clean: see Interference and SUTVA
- Question is "how big is the effect?" rather than "does it cause" — descriptive analytics is enough
- No plausible causal mechanism — correlation is just measurement, not insight
- Sample size too small for propensity overlap (n < 1000 typical) — flag and collect more data
- E-value < 1.5 from sensitivity analysis — claim is fragile; do not ship as causal
- Question is about strategic interaction (multi-actor) — use foundations-game-theory
What ships with it
20 files 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.
- agents/openai.yaml 366 B
- assets/templates/causal-inference/01-dag-scm.md 3.6 KB
- assets/templates/causal-inference/02-do-calculus.md 4.4 KB
- assets/templates/causal-inference/03-backdoor-frontdoor.md 3.9 KB
- assets/templates/causal-inference/04-instrumental-variables.md 4.2 KB
- assets/templates/causal-inference/05-rdd.md 4.4 KB
- assets/templates/causal-inference/06-diff-in-diff.md 5.8 KB
- assets/templates/causal-inference/07-synthetic-control.md 4.4 KB
- assets/templates/causal-inference/08-propensity-score.md 4.8 KB
- assets/templates/causal-inference/09-cate-uplift.md 4.9 KB
- assets/templates/causal-inference/10-simpsons-paradox.md 4.8 KB
- assets/templates/causal-inference/11-mediation-analysis.md 5.1 KB
- assets/templates/causal-inference/12-sensitivity-analysis.md 5.4 KB
- assets/templates/causal-inference/README.md 4.6 KB
- data/sources.json 20 KB
- learnings.consolidated.md 604 B
- learnings.md 628 B
- references/formal-theory-map.md 3.6 KB
- references/patterns-scenarios-traps.md 5.5 KB
- references/primitives-overview.md 23 KB
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.
- 9d ago First seen · 360 lines · 0 tokens per session scan A 35d6dc1d2bcd
foundations-causal-inference is a skill published in the GitHub repository vasilyu1983/AI-Agents-public (87 stars, last pushed 10d ago), licensed MIT. It adds 51 tokens to every session and 8,364 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
projection-patterns
Build read models and projections from event streams. Use when implementing CQRS read sides, building materialized views, or optimizing query performance in event-sourced systems.
microservices-patterns
Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.
track-management
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
make-pr-easy-to-review
Prepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior. Use for "make this easy to review", "tidy this PR", "clean up commits", or "annotate the diff".