causal-design

causal-design is a skill for Claude Code from flonat/flonat-research. It costs 40 tokens per session (2,390 once invoked), scanned A, original, MIT.

A workflow for designing or reviewing how an observational study can support causal conclusions. An identification strategy states what must be true for the estimated effect to be credible.

In plain words
What is it for?
It examines estimands, causal assumptions, and research-design choices rather than model implementation.
Why use it?
It exposes weak assumptions and threats that could make an apparent relationship misleading.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions subagents; names the AskUserQuestion tool.

Good fit It examines estimands, causal assumptions, and research-design choices rather than model implementation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/flonat/flonat-research/causal-design
Install

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.

Any agent
npx skills add flonat/flonat-research --skill causal-design
Clone the repo
git clone --depth 1 https://github.com/flonat/flonat-research

Made for: Claude Code.

Wrote 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.

agentmods badge for causal-design

README.md
[![agentmods](https://agentmods.dev/badge/skills/flonat/flonat-research/causal-design/github.svg)](https://agentmods.dev/skills/flonat/flonat-research/causal-design)
Your own site
<a href="https://agentmods.dev/skills/flonat/flonat-research/causal-design"><img src="https://agentmods.dev/badge/skills/flonat/flonat-research/causal-design/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.

agentmods 80×15 button for causal-design

Your own site · 80×15
<a href="https://agentmods.dev/skills/flonat/flonat-research/causal-design"><img src="https://agentmods.dev/badge/skills/flonat/flonat-research/causal-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,390 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00040 $0.02390
Opus 5 $0.00020 $0.01195
Sonnet 5 $0.00008 $0.00478
Haiku 4.5 $0.00004 $0.00239

Measured 5d ago against content hash 94e4b3b5fb36, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

causal-design 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 5d 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.

skills/causal-design/SKILL.md · 245 lines

How it starts

The opening of the file, as written. The whole thing — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Causal Design

Design and audit identification strategies for observational causal inference.

Output Path

Per rules/review-artefact-routing.md (auto-loads in research projects (path-scoped to paper-*/ and paper/)):

  • Source slug: causal-design
  • Write reports to: reviews/<scope>/causal-design/<YYYY-MM-DD-HHMM>.md inside the project, where <scope> is the paper slug (e.g. paper-philtech) for paper-level audits or _project for project-level reviews. Path is relative to the research project root, not the Task-Management repo.
  • Never at project root (./CRITIC-REPORT.md-style filenames are forbidden — pre-rule layout).
  • Idempotency: if today's timestamp exists, append a same-day descriptor to the path base ({date}-HHMM-revision.md, {date}-HHMM-r2.md, {date}-HHMM-pre-submission.md) — never overwrite.
  • Index update: if reviews/INDEX.md exists, write a one-line entry under "Latest per source" pointing at the new file. Otherwise review-recap will rebuild the index next time it runs.
  • Infrastructure repos (Task-Management, atlas-workspace, etc.): this section does not apply — the path-scoped rule won't load there.

Modes

Mode What it does Entry point
Design Interview-driven strategy selection and memo production "Design my causal strategy" / "What identification can I use?"
Audit 4-phase causal inference check on existing paper/scripts "Check my identification" / "Audit my econometrics"

Default: Design. If the user points to an existing paper or estimation script, auto-select Audit mode.

When to Use

  • Choosing an identification strategy for an observational study
  • Stress-testing whether an existing strategy is credible
  • Verifying that code implements the claimed identification design
  • Mapping causal claims to their identifying assumptions

When NOT to Use

  • Experimental design (RCTs, surveys, factorial) -- use experiment-design
  • Running the analysis or generating results -- use data-analysis
  • Literature search or citation gathering -- use an installed literature workflow or scholarly search
  • Proofreading or compiling the paper -- use proofread, latex

Read the full file on GitHub · 245 lines

Files

What ships with it

3 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.

Changes

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.

  1. 5d ago First seen · 245 lines · 40 tokens per session scan A 94e4b3b5fb36

Subscribe to this mod's changes

causal-design is a skill published in the GitHub repository flonat/flonat-research (132 stars, last pushed 14d ago), licensed MIT. It adds 40 tokens to every session and 2,390 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-09-03.

Related

Other skills, from other repositories

latex-compile

Compile a LaTeX document and fix every error plus aesthetic issue (overfull/underfull boxes, widows, alignment, fonts) for a clean PDF and log. Use this instead of running pdflatex/latexmk manually — it avoids the latexmk stale-log trap and silent grep failures on binary log output, and it reformats rather than…

Mexregkan/claude-for-researchers · 79 tokens

nb-to-wolfbook

Convert Mathematica .nb or .m files to Wolfbook .wb format so they open and run in VS Code. Use when bringing existing .nb/.m files into Wolfbook, or to make an existing .wb bridge-safe.

Mexregkan/claude-for-researchers · 53 tokens

sync-wb-nb

Propagate a change made in a Wolfbook .wb notebook into the paired .nb notebook so the two stay identical. Use immediately after every .wb edit.

Mexregkan/claude-for-researchers · 38 tokens

wolfram-headless

Run heavy Wolfram Language (wolframscript) computations from Claude Code reliably, and diagnose the misleading "The product exited because of a license error". Use whenever invoking wolframscript on a non-trivial computation, when a wolframscript job dies with a "license error" despite a valid license, or when Wolfram…

Mexregkan/claude-for-researchers · 84 tokens

cross-validate

Format a result, derivation, or numerical value for independent verification by a second model. Use when you want a cross-check on an important or contested result.

Mexregkan/claude-for-researchers · 36 tokens

verify-citation

Confirm a paper actually exists (arXiv / Semantic Scholar / OpenAlex) before citing it. Use before writing any new citation.

Mexregkan/claude-for-researchers · 31 tokens