claude-code-my-workflow is a forkable setup for using Claude Code to produce and review academic papers, slides, data analyses, and replication packages. Researchers use its agents, skills, rules, hooks, and quality checks to coordinate these tasks and verify their results. The catalogue entries define the reusable workflow components for Claude Code.
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 pedrohcgs/claude-code-my-workflow --skill preregistergit clone --depth 1 https://github.com/pedrohcgs/claude-code-my-workflowWrote 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/pedrohcgs/claude-code-my-workflow/preregister)<a href="https://agentmods.dev/skills/pedrohcgs/claude-code-my-workflow/preregister"><img src="https://agentmods.dev/badge/skills/pedrohcgs/claude-code-my-workflow/preregister/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/pedrohcgs/claude-code-my-workflow/preregister"><img src="https://agentmods.dev/badge/skills/pedrohcgs/claude-code-my-workflow/preregister.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 129 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 130 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 131 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00153 | $0.02980 |
| Opus 5.5 | $0.00061 | $0.01192 |
| Sonnet 5.5 | $0.00031 | $0.00596 |
| Haiku 4.5 | $0.00015 | $0.00298 |
Grade A, and why
preregister 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 28d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- preregister — 89% identical, 18 lines differ
How it starts
The opening of the file, as written. The whole thing — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/preregister — Preregistration Document Generator
Produce a registry-ready preregistration document. The user uploads it to a real registry (OSF / AsPredicted / AEA RCT Registry) — this skill writes the prose and structure, it does not submit anywhere.
Why preregister
Preregistration is a written commitment to your hypotheses, design, and analysis plan before you see the data (or, for observational analyses, before you analyse the realised outcome). It separates confirmatory tests from exploratory tests and protects you from p-hacking, HARKing, and forking-paths. Different fields use different registries:
- Political science, psychology, broad social science → OSF (osf.io/registries) is the default. AsPredicted (aspredicted.org) is a popular short form for experiments.
- Economics field experiments → AEA RCT Registry (socialscienceregistry.org) is mandatory for AEA journal submission since 2018.
- Public health / clinical trials → ClinicalTrials.gov or ISRCTN (NOT covered by this skill — use the trial-registry's own template).
When to use
- Before launching an experiment (lab, field, or survey).
- Before collecting observational data on a target population for a specific RQ.
- Before analysing data you have access to but haven't yet examined for the focal hypothesis.
- During R&R when a referee asks for a written preanalysis plan.
When NOT to use
- After you've seen the realised outcomes and want to "preregister retrospectively" — that is not preregistration. The skill will refuse if the input description includes results.
- For exploratory analyses — those don't need preregistration; they need transparent labelling.
- For meta-analyses — use PROSPERO directly, not this template.
Workflow
PHASE 1 — Read inputs
Two input modes:
--input <path>— a research spec produced by/interview-me(saved underquality_reports/specs/) or any structured Markdown file. Read the spec and extract: research question, hypotheses (directional!), data source, design, sample, analysis approach. If the spec records a paper type (/interview-mewrites it on a**Paper type:**line, e.g.survey-experiment), use it to bias the style choice.- No
--input— prompt the user for a 1–3 paragraph description of the study, then proceed. If the description omits a directional hypothesis, ask once. Do not fabricate.
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.
- 28d ago Changed ad15982ed8d7
- 1mo ago First seen · 173 lines · 153 tokens per session scan A f7a4395f45bd
preregister is a skill published in the GitHub repository pedrohcgs/claude-code-my-workflow (1,668 stars, last pushed 29d ago), licensed MIT. It adds 153 tokens to every session and 2,980 once invoked, about $0.0006 per session on Opus 5.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 skills, from other repositories
fin-paper-figure
Generate academic-quality figures (>=300 DPI) for economics and finance papers.
fin-paper-writing
A workflow for turning a research outline and study design into a complete economics or finance paper. It coordinates drafting, figure creation, consistency checks, review rounds, LaTeX compilation, and submission checks.
fin-viz-launch
A tool for turning research data and a written description into academic charts. It can choose a suitable chart type, create plotting code with matplotlib or seaborn, and save the result as a high-resolution PDF, SVG, or PNG.
fin-data-acquisition
A data-preparation workflow for financial research. It reads variable definitions from a completed research design and produces data-acquisition work plus executable Python or Stata regression scripts.
fin-lit-review
A systematic literature-review workflow for economics and finance. It searches several academic sources, maps how papers cite one another, and organizes the main findings and research gaps.
fin-submit-check
A pre-submission checklist for an academic paper and its LaTeX files. It checks journal requirements such as anonymous authorship, length, spacing, margins, citations, figures, data availability, and other submission details.