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 skills/lancegui/causal-powers/project-organizationnpx skills add lancegui/causal-powers --skill project-organizationgit clone --depth 1 https://github.com/lancegui/causal-powersWrote 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/lancegui/causal-powers/project-organization)<a href="https://agentmods.dev/skills/lancegui/causal-powers/project-organization"><img src="https://agentmods.dev/badge/skills/lancegui/causal-powers/project-organization.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.00202 | $0.02713 |
| Opus 5 | $0.00101 | $0.01357 |
| Sonnet 5 | $0.00040 | $0.00543 |
| Haiku 4.5 | $0.00020 | $0.00271 |
Grade A, and why
project-organization 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Organization
Overview
A research repository has one destination — the paper — and one test: six months in, a collaborator (or future you) opens it and must answer fast — what is a finished result, what is scratch, and how was each number produced? Organization makes the work reproducible and legible to someone who wasn't in the conversation — analysis-craft's clean-diff discipline, scaled to the directory.
Core principle: organize around the paper and its pipeline; place and name every artifact so its role (deliverable / intermediate / raw) and its producer are obvious; and before you commit, tidy so the repo shows deliverables and code, not scratch.
The structure
project-root/
├── README.md # the map: what this is, data provenance, one-command reproduction
├── paper/ # the destination — manuscript + the FINAL tables/figures it uses
├── data/
│ ├── raw/ # original, immutable — code reads it, never writes it
│ ├── intermediate/ # cleaned / merged working data (reproducible)
│ └── output/ # analysis-ready datasets the analysis reads
│ └── mortality/ crime/ … # subject subfolders where the project spans several
├── code/ # pipeline ordered by paper stage (R / Julia / Python / Stata)
│ ├── 00_data/ # raw → intermediate → output ── subjects: mortality/ crime/ …
│ ├── 01_stylized_facts/
│ ├── 02_main/ # ── subjects: did_mortality/ did_crime/ …
│ │ └── archive/ # superseded runs for this category — kept, not deleted, out of the active path
│ ├── 03_estimation/ 04_montecarlo/ 05_robustness/ 06_counterfactual/ # (structural)
│ └── lib/ # shared functions
├── results/ # generated artifacts — tables/ figures/ (canonical) · diagnostics/ (scratch) · archive/ (old runs, kept)
├── docs/
│ ├── analysis/ # index.yaml + compact phase/decision/artifact state
│ ├── MODEL_CARD.md
│ ├── pre-analysis-plan.md
│ └── LESSONS.md
├── sandbox/ # exploratory throwaway, clearly not a deliverable
└── .gitignore
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 · 120 lines · 202 tokens per session scan A 0b90dd974cdd
project-organization is a skill published in the GitHub repository lancegui/causal-powers (2 stars, last pushed 11d ago), licensed MIT. It adds 202 tokens to every session and 2,713 once invoked, about $0.0010 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.
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.
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…
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…
grant-proposal
Scaffold a research grant proposal (NSF, NIH, ERC, or foundation) by composing existing primitives — pulls identification strategy from an /interview-me spec, delegates the data-management plan to /data-management-plan and the facilities statement to /capture-environment, and emits a funder-requirements checklist. Use…
preregister
Draft a structured preregistration document (OSF, AsPredicted, or AEA RCT Registry style) from a research spec or free-form study description. Output is a Markdown file with hypotheses, design, sampling plan, analysis plan, exclusions, and inference criteria — annotated with MUST / SHOULD / MAY clarity flags. Use when…
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…