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 verify-claimsgit 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/verify-claims)<a href="https://agentmods.dev/skills/pedrohcgs/claude-code-my-workflow/verify-claims"><img src="https://agentmods.dev/badge/skills/pedrohcgs/claude-code-my-workflow/verify-claims/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/verify-claims"><img src="https://agentmods.dev/badge/skills/pedrohcgs/claude-code-my-workflow/verify-claims.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Agent Snooping · line 81 Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
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.00137 | $0.02096 |
| Opus 5 | $0.00068 | $0.01048 |
| Sonnet 5 | $0.00027 | $0.00419 |
| Haiku 4.5 | $0.00014 | $0.00210 |
Grade A, and why
verify-claims 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 6d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/verify-claims — Chain-of-Verification on a Draft
Fact-check a draft using the Post-Flight Verification protocol (.claude/rules/post-flight-verification.md).
Input: $ARGUMENTS — path to a file containing the draft (markdown, .qmd, .tex, .md) or a shorthand pointer. Optional flags:
--source <path-or-url>— one or more source-material pointers (repeat for multiple). If omitted, the skill infers from context (e.g., papers referenced, cited arXiv URLs).--no-fail-closed— downgrade FAIL outcomes to warnings without regeneration. Use sparingly.
When to pick this skill
/verify-claims(this skill) — ad-hoc fact-checking on any draft or text block the user hands you. One-shot, user-invoked.- Other skills that auto-run Post-Flight internally (
/lit-review,/research-ideation,/respond-to-referees,/review-paper --peer) — no need to call this separately; they already run it. /proofread— grammar, typos, overflow. Different lens./review-paper(default mode) — full manuscript review, not just claim verification./validate-bib— checks citations exist and are well-formed (structural + DOI). This skill checks they hold (the cited paper supports the attributed claim). Complementary — run both before submission.
How it works
Implements the 4-step CoVe loop from Dhuliawala et al. 2023 (arXiv:2309.11495), with architectural enforcement of the fresh-context independence trick.
Phase 0 — Pre-Flight
Confirm:
- Draft file exists and is readable
- At least one source pointer available (either
--sourceor auto-detected from draft) claim-verifieragent file exists at.claude/agents/claim-verifier.md
If any fail → surface the failure, do NOT proceed.
Phase 1 — Extract claims
Read the draft. Identify factual assertions of these types:
| Type | Example |
|---|---|
| Citation | "Smith (2019, JEL) shows X" |
| Numerical fact | "N = 10,000", "ATT = 0.42" |
| Negative literature | "No prior work studies X" |
| Named entity | researcher, paper title, venue, package, estimator name |
| Dataset claim | "The CPS contains field educ_attain" |
What ships with it
2 files 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.
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.
- 6d ago First seen · 142 lines · 137 tokens per session scan A 8f1cd669767a
verify-claims is a skill published in the GitHub repository pedrohcgs/claude-code-my-workflow (1,570 stars, last pushed 16d ago), licensed MIT. It adds 137 tokens to every session and 2,096 once invoked, about $0.0007 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-09-03.
Other skills, from other repositories
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.
r-econometrics
Run IV, DiD, and RDD analyses in R with proper diagnostics.
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.