descriptive-evidence

descriptive-evidence is a skill for Claude Code, Codex from lancegui/causal-powers. It costs 228 tokens per session (5,112 once invoked), scanned A, original, MIT.

A guide for describing what is present in a dataset, such as trends, gaps, distributions, maps, and summary tables. It focuses on reporting the data accurately rather than explaining causes or making predictions.

In plain words
What is it for?
Preparing descriptive statistics, charts, maps, trend summaries, and opening evidence for empirical research.
Why use it?
It helps prevent misleading conclusions caused by aggregation, changing group composition, or other features of the data.

Skill for Claude CodeCodex

Part of the causal-powers plugin — 18 skills, 2 agents, 5 hooks shipped together

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.

agentmods
npx agentmods add skills/lancegui/causal-powers/descriptive-evidence
Any agent
npx skills add lancegui/causal-powers --skill descriptive-evidence
Clone the repo
git clone --depth 1 https://github.com/lancegui/causal-powers

Made for: Claude Code, Codex.

Or install causal-powers, the plugin that ships this one along with the rest of its 18 skills, 2 agents, 5 hooks.

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 descriptive-evidence

README.md
[![agentmods](https://agentmods.dev/badge/skills/lancegui/causal-powers/descriptive-evidence.svg)](https://agentmods.dev/skills/lancegui/causal-powers/descriptive-evidence)
Your own site
<a href="https://agentmods.dev/skills/lancegui/causal-powers/descriptive-evidence"><img src="https://agentmods.dev/badge/skills/lancegui/causal-powers/descriptive-evidence.svg" alt="Measured on agentmods" height="20"></a>
Per session 228 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,112 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00228 $0.05112
Opus 5 $0.00114 $0.02556
Sonnet 5 $0.00046 $0.01022
Haiku 4.5 $0.00023 $0.00511

Measured 4d ago against content hash 95d312034487, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

descriptive-evidence 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.

skills/descriptive-evidence/SKILL.md · 177 lines

How it starts

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

Descriptive Evidence

Overview

Causal identification asks what an intervention did; structural estimation asks what a world we haven't seen would do; prediction asks what is likely true of a unit, so I can act on it. Beneath all three sits the work the discipline rushes past: describing what is actually in the data — the trend, the gap, the distribution, the summary-statistics table, the stylized facts that open almost every empirical paper. The deliverable is a faithful picture of the data — often the whole job, otherwise the thing that motivates the causal, structural, or predictive question that follows.

This is a legitimate destination, not a way-station: "just show me the trend" does not mean "skip the rigor" — it means the rigor is about the description itself.

The signature failure of this arm is the composition / aggregation artifact — a trend or gap that looks within-group but is really a shift in the mix (the aggregate wage rose because low-wage workers exited, not because anyone got a raise; a national rate can fall while it rises in every region — Simpson's paradox). It reconciles, reproduces, and plots beautifully while quietly describing the denominator or the changing sample, not the thing you named — the descriptive analog of leakage: a confident artifact.

The twin failure is the descriptive-to-causal slide: Y rises alongside X, and the write-up says "X raised Y." A described co-movement is a correlation; the moment it wears a causal verb it has left this arm for a claim it hasn't earned. A striking stylized fact's highest use is to motivate a causal question, which routes to causal-identification and earns the causal verb there — not here.

Core principle: a descriptive fact is trustworthy only when it survives the ordinary alternative explanations for the pattern — composition, deflation, scaling, selection, definition — and is stated as the correlation it is, not the cause it isn't. Everything below serves that one sentence.

Read the full file on GitHub · 177 lines

Files

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.

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. 4d ago First seen · 177 lines · 228 tokens per session scan A 95d312034487

Subscribe to this mod's changes

descriptive-evidence is a skill published in the GitHub repository lancegui/causal-powers (2 stars, last pushed 11d ago), licensed MIT. It adds 228 tokens to every session and 5,112 once invoked, about $0.0011 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-31.

Related

Other skills, from other repositories

audit-reproducibility

Enforce the replication-protocol.md rule by cross-checking numeric claims in a manuscript against the actual R / Stata / Python outputs. Report PASS/FAIL per claim against tolerance thresholds. Use before submission and before releasing a replication package.

pedrohcgs/claude-code-my-workflow · 54 tokens

review-paper

Comprehensive manuscript review with three modes: single-pass (default), --adversarial critic-fixer loop, and --peer [journal] simulated peer-review pipeline (editor + 2 dispositioned referees + editorial decision, calibrated to a target journal). R&R continuation via --peer --r2/--r3; hostile-editor stress test via…

pedrohcgs/claude-code-my-workflow · 114 tokens

diagnose

Root-cause a failing or wrong empirical result with a disciplined reproduce → minimise → hypothesise → instrument → fix loop, instead of guessing-and-poking. Use when the user says "why is my regression wrong", "this number changed", "my script errors out", "the result won't reproduce", "debug this", "this estimate…

pedrohcgs/claude-code-my-workflow · 0 tokens

capture-environment

Snapshot the computational environment for a replication package — detects the analysis stack (R / Stata / Python) and emits the right lockfiles (renv.lock + sessionInfo.txt, requirements.txt / environment.yml / uv.lock, Stata version + ado package list), records seeds and RNG kind, optionally writes a pinning…

pedrohcgs/claude-code-my-workflow · 139 tokens

checkpoint

Save a structured state snapshot before stopping or handing off. Captures the active plan, recent decisions, file pointers (with line numbers), open questions, and the next 1–3 actions into a checkpoint file under qualityreports/checkpoints/. Optionally proposes [LEARN] entries to add to MEMORY.md. Use when user says…

pedrohcgs/claude-code-my-workflow · 124 tokens

coauthor-brief

Generate a co-author / collaborator handoff brief for a multi-author, multi-machine project — summarizing what changed since the last brief (git delta), the current state of each artifact (manuscript, analysis, slides), open questions, how to reproduce locally, and any restricted-data access steps. Use when user says…

pedrohcgs/claude-code-my-workflow · 146 tokens