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 checkpointgit 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/checkpoint)<a href="https://agentmods.dev/skills/pedrohcgs/claude-code-my-workflow/checkpoint"><img src="https://agentmods.dev/badge/skills/pedrohcgs/claude-code-my-workflow/checkpoint/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/checkpoint"><img src="https://agentmods.dev/badge/skills/pedrohcgs/claude-code-my-workflow/checkpoint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 78 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.00124 | $0.02785 |
| Opus 5.5 | $0.00050 | $0.01114 |
| Sonnet 5.5 | $0.00025 | $0.00557 |
| Haiku 4.5 | $0.00012 | $0.00279 |
Grade A, and why
checkpoint 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 22d 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:
- checkpoint — 86% identical, 35 lines differ
How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/checkpoint — Structured Session Handoff
Produce a state snapshot that the next session (yours, or a collaborator's, or a fresh-context reboot) can resume from in under a minute. The narrative quality_reports/session_logs/ continues to live separately — /checkpoint writes the structured side: facts, file pointers, and next-actions.
When to use
- Before a long break, model switch (Opus ↔ Sonnet ↔ Haiku), or end of a working day.
- Before auto-compaction would otherwise discard mid-plan context (paired with the PreCompact hook).
- Before handing off to a collaborator on the same repo.
- After completing a chunk of a multi-session plan, when "where am I" is the first question the next session will ask.
When NOT to use
- For the narrative what happened — that lives in
quality_reports/session_logs/(see.claude/rules/session-logging.md). - For commit messages — those go through
/commit, which writes its own structured commit body. - For decisions about alternatives — those go to
templates/decision-record.mdviaquality_reports/decisions/.
The three artifact types are complementary: session-log = narrative, decision-record = trade-off captured, checkpoint = state to resume from.
Workflow
PHASE 1 — Gather state
Read, in this order:
- Most recent plan —
ls -t quality_reports/plans/*.md | head -1. Extract: status (DRAFT / APPROVED / COMPLETED), title, top-level files-to-modify list, and any line that begins with "Open questions" / "Risks" / "Next". - Most recent session log —
ls -t quality_reports/session_logs/*.md | head -1. Extract: latest "Next steps" or "Blockers" lines. - MEMORY.md root — read the table of
[LEARN]entries already on disk so you don't propose duplicates. - Git state —
git log --oneline -20,git status -s,git branch --show-current. Capture: current branch, last 5 subjects, uncommitted file count. - Working files —
git diff --stat HEADto see which files changed in this session (skip if branch is freshly cut; just say "no in-session edits"). - Active TODOs — if a TodoWrite list is in flight in this session, capture the in-progress + next-pending items.
- In-flight background work — anything this session started and did not wait for: a long-running compute job, a scheduled routine (
.claude/references/scheduled-routines.md), a queued render or compile, an external review still out with a referee or another model. For each, record four things: what is running, where its artifacts land, the command that checks on it, and the verdict that ends it.
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.
- 22d ago Changed · +10 lines 3a8bf95080a5
- 1mo ago First seen · 172 lines · 124 tokens per session scan A f671faa7ceb5
checkpoint is a skill published in the GitHub repository pedrohcgs/claude-code-my-workflow (1,664 stars, last pushed 22d ago), licensed MIT. It adds 124 tokens to every session and 2,785 once invoked, about $0.0005 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
r-econometrics
Run IV, DiD, and RDD analyses in R with proper diagnostics.
paper-workflow
A staged workflow for producing an evidence-based economics or social-science research paper, from choosing a topic through submission. It coordinates existing tools and analysis options, including Python, Stata, and R.
econ-management-paper-polish
A writing and editing guide for papers in economics, management, finance, accounting, marketing, information systems, public administration, and related fields.
did-causal
Use this Skill when the user needs to estimate causal treatment effects using difference-in-differences (DID) designs: two-way fixed effects (TWFE) regression, parallel trends pre-testing, Callaway-Sant'Anna staggered adoption estimator, and Goodman-Bacon decomposition. Covers both Python (linearmodels) and R (did…
fin-paper-convert
Compile LaTeX to PDF and convert to target journal format.
fin-paper-figure
Generate academic-quality figures (>=300 DPI) for economics and finance papers.