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
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/pedrohcgs/claude-code-my-workflownpx agentmods add skills/pedrohcgs/claude-code-my-workflow/commitWrote 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/commit)<a href="https://agentmods.dev/skills/pedrohcgs/claude-code-my-workflow/commit"><img src="https://agentmods.dev/badge/skills/pedrohcgs/claude-code-my-workflow/commit/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/commit"><img src="https://agentmods.dev/badge/skills/pedrohcgs/claude-code-my-workflow/commit.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.00135 | $0.02238 |
| Opus 5.5 | $0.00054 | $0.00895 |
| Sonnet 5.5 | $0.00027 | $0.00448 |
| Haiku 4.5 | $0.00014 | $0.00224 |
Grade A, and why
commit 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 19d 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit
Verify the gates, then commit. A commit is not a pull request, and a pull request is not a merge.
This skill stops after the commit. It pushes and opens a pull request only with --pr or when the
user asks, and it never merges — a merge happens only when the user explicitly says to merge
that pull request (see "Merging" below). Reviewers such as Codex and Copilot comment after a pull
request opens; merging before they report skips their review.
Steps
Step 0: Quality Gate (Pre-Commit)
Run before branching. For every changed .qmd, .tex, or .R file that has quality rubrics, run:
python3 scripts/quality_score.py <changed-file-paths>
- If any file scores below 80, halt and report the findings. The user must either fix the issues or explicitly override with phrases like "commit anyway" or "skip quality gate". Once
./scripts/install-hooks.shhas been run,.githooks/pre-commitre-runs the same ≥80 gate on the staged.qmd/.tex/.Rfiles, so carry an approved override into Step 4 asSKIP_QUALITY_GATE=1 git commit ...and record the override reason in the commit message. That variable skips only the quality score; the backtest still runs. Never fall back togit commit --no-verify. - If all files score 80+, continue.
Spawn the verifier agent (via the Agent tool with subagent_type=verifier) to run compilation/render checks on the changed files. Report pass/fail before committing.
Step 0b: Consistency Gate (Pre-Commit)
Runs unconditionally. The full backtest suite — all ten gates (surface-sync count claims like "18 agents, 61 skills, 37 rules, 11 hooks" and marked tables, skill integrity, model currency, links, spec conformance, staleness, repo hygiene, derived counts, ledger coverage, hook battery):
./scripts/backtest.sh
- Exit 0: all gates green — continue.
- Nonzero: at least one gate is red — print its output and halt. Fix, then re-run. Do not proceed past this gate on a red result, even with "commit anyway": a red gate is drift that the next reader inherits, and small count drift has repeatedly cost follow-up PRs.
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.
- 19d ago Changed · +26 lines · +30 tokens per session 899017f9ba57
- 1mo ago First seen · 147 lines · 105 tokens per session scan A 361ca7da5bc3
commit is a skill published in the GitHub repository pedrohcgs/claude-code-my-workflow (1,662 stars, last pushed 19d ago), licensed MIT. It adds 135 tokens to every session and 2,238 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
attribution
Commit authorship policy — no co-author trailers, user is sole author.
what-did-i-get-done
Summarize authored commits over a user-specified time period into a concise update.
pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
phx-pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
private-secret-scanning
Local Gitleaks scans for staged changes, push ranges, and full history in private repos, with redacted reports. Use to block committed secrets without GitHub Secret Protection.
ln-61-repository-publisher
Commits, pushes and remotely verifies authorized repository changes; does not create releases.