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 deploygit 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/deploy)<a href="https://agentmods.dev/skills/pedrohcgs/claude-code-my-workflow/deploy"><img src="https://agentmods.dev/badge/skills/pedrohcgs/claude-code-my-workflow/deploy/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/deploy"><img src="https://agentmods.dev/badge/skills/pedrohcgs/claude-code-my-workflow/deploy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00081 | $0.00518 |
| Opus 5.5 | $0.00032 | $0.00207 |
| Sonnet 5.5 | $0.00016 | $0.00104 |
| Haiku 4.5 | $0.00008 | $0.00052 |
Grade A, and why
deploy 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 1mo 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.
What it actually says
Deploy Slides to GitHub Pages
Render Quarto slides and sync all files to docs/ for GitHub Pages deployment.
Steps
-
Run the sync script:
- If
$ARGUMENTSis provided (e.g., "Lecture4"):./scripts/sync_to_docs.sh $ARGUMENTS - If no argument:
./scripts/sync_to_docs.sh(syncs all lectures)
- If
-
Verify deployment:
- Check that HTML files exist in
docs/slides/ - Check that
_files/directories were copied (RevealJS assets) - Check that
docs/Figures/was synced fromFigures/ - Check that
docs/files/code/contains the R scripts (ifscripts/R/has any)
- Check that HTML files exist in
-
Verify interactive charts (if applicable):
- Grep rendered HTML for interactive widget count
- Confirm count matches expected
-
Verify TikZ SVGs (if applicable):
- Check that all referenced SVG files exist in
docs/Figures/LectureN/
- Check that all referenced SVG files exist in
-
Open in browser for visual verification:
open docs/slides/LectureX_Name.html# macOS# xdg-open docs/slides/LectureX_Name.html# Linux- Confirm slides render, images display, navigation works
-
Report results to the user
What the sync script does:
- Renders all
.qmdfiles inQuarto/(skips*_backup*files) - Copies HTML and
_files/directories todocs/slides/ - Copies Beamer PDFs from
Slides/todocs/slides/ - Syncs
Figures/todocs/Figures/using rsync - Copies every
scripts/R/*.Rintodocs/files/code/(published beside the slides)
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.
- 1mo ago First seen · 44 lines · 81 tokens per session scan A 0151e604dcc5
deploy is a skill published in the GitHub repository pedrohcgs/claude-code-my-workflow (1,664 stars, last pushed 22d ago), licensed MIT. It adds 81 tokens to every session and 518 once invoked, about $0.0003 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…
activate-site
Activates and provisions a Power Pages website in a Power Platform environment via the Power Platform REST API. Use when the user wants to activate, provision, turn on, or enable a Power Pages website or portal.
deploy-site
Deploys an existing Power Pages code site to a Power Pages environment using PAC CLI. Handles tooling verification, authentication, environment confirmation, building, and uploading. Use when the user wants to deploy, upload, or publish their code site.