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.
git 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/agents/pedrohcgs/claude-code-my-workflow/domain-reviewer)<a href="https://agentmods.dev/agents/pedrohcgs/claude-code-my-workflow/domain-reviewer"><img src="https://agentmods.dev/badge/agents/pedrohcgs/claude-code-my-workflow/domain-reviewer/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/agents/pedrohcgs/claude-code-my-workflow/domain-reviewer"><img src="https://agentmods.dev/badge/agents/pedrohcgs/claude-code-my-workflow/domain-reviewer.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00056 | $0.01915 |
| Opus 5 | $0.00028 | $0.00958 |
| Sonnet 5 | $0.00011 | $0.00383 |
| Haiku 4.5 | $0.00006 | $0.00192 |
Grade A, and why
domain-reviewer 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 9d 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scope: general substantive reviewer for academic content (slides and manuscripts), NOT disposition-primed. Used by
/slide-excellence(slide context) and/seven-pass-review(manuscript methods/identification lens). For the disposition-primed manuscript peer-review variant driven by/review-paper --peer, seedomain-referee.md— same domain expertise, but with an editor-assigned disposition + pet peeves.
You are a top-journal referee with deep expertise in your field. You review lecture slides for substantive correctness.
Your job is NOT presentation quality (that's other agents). Your job is substantive correctness — would a careful expert find errors in the math, logic, assumptions, or citations?
Your Task
Review the lecture deck through 5 lenses. Produce a structured report. Do NOT edit any files.
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.
- 9d ago First seen · 204 lines · 56 tokens per session scan A 9fb66a7d6eb3
domain-reviewer is an agent published in the GitHub repository pedrohcgs/claude-code-my-workflow (1,567 stars, last pushed 15d ago), licensed MIT. It adds 56 tokens to every session and 1,915 once invoked, about $0.0003 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-30.
Other agents, from other repositories
domain-reviewer
Substantive domain review for lecture slides. Template agent — customize the 5 review lenses for your field. Checks derivation correctness, assumption sufficiency, citation fidelity, code-theory alignment, and logical consistency. Use after content is drafted or before teaching.
simulator
Monte Carlo Simulation Pipeline — DGP design and execution.
robustness-runner
Executes ONE pre-specified task against an already-validated dataset or model — a robustness specification, placebo/falsification test, alternative design, subsample cut, or a structural unit of work (a Monte-Carlo recovery rep at a given true-θ / seed / starting value, or one counterfactual scenario with a stated…
stata-analyst
End-to-end statistical analysis agent for Stata. Handles the full workflow from data loading through estimation, results retrieval, and graph export. Invoke when user wants a complete analysis, asks to "run a regression", "analyze this dataset", or describes a multi-step econometric workflow.
stata-replication-lead
Specialist agent for replication, robustness, and multi-specification evidence gathering in Stata. Invoke when the user needs a paper result reproduced, a pipeline rerun, or a structured robustness campaign.
stata-publication-reviewer
Specialist agent for publication-ready Stata outputs. Invoke when the user needs a hard-nosed review of tables, figures, model notes, or appendix materials before sharing them with coauthors, seminar audiences, or referees.