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 triage-inboxgit 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/triage-inbox)<a href="https://agentmods.dev/skills/pedrohcgs/claude-code-my-workflow/triage-inbox"><img src="https://agentmods.dev/badge/skills/pedrohcgs/claude-code-my-workflow/triage-inbox/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/triage-inbox"><img src="https://agentmods.dev/badge/skills/pedrohcgs/claude-code-my-workflow/triage-inbox.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, 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 107 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.
- medium Agent Snooping · line 108 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.00132 | $0.02368 |
| Opus 5 | $0.00066 | $0.01184 |
| Sonnet 5 | $0.00026 | $0.00474 |
| Haiku 4.5 | $0.00013 | $0.00237 |
Grade A, and why
triage-inbox 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/triage-inbox — Academic Inbox + Calendar Triage
Turn a noisy academic inbox into a short, decision-ready digest. Fetch recent mail and calendar context through the session's MCP servers (Gmail / Google Calendar), classify each thread into the categories an academic actually acts on, and propose one action per thread — always human-gated. The companion artifact is a running referee-obligations tracker so you never silently overcommit to reviews.
Core principle: this skill reads, classifies, and proposes. It drafts; it never sends, accepts, declines, or books anything without you. That boundary is what makes it safe to run unattended as a /schedule routine.
When to use
- Weekly / daily sweep — "what landed that needs a decision?" without reading every thread yourself.
- As a scheduled routine — wired to
/scheduleto run each morning and leave a digest waiting. - Referee-load management — keep an honest count of outstanding reviews against a standing cap before you say yes to one more.
- R&R / editor deadline capture — turn "minor revision due in 6 weeks" buried in an email into a calendar hold proposal.
When NOT to use
- To actually send a reply, accept an invite, or book an event — this skill stops at proposals. You confirm and execute.
- To handoff a project to a co-author — that's
/coauthor-brief. - To draft the R&R response document itself — that's
/respond-to-referees.
Phases
Phase 0 — Pre-flight (MCP check, window, referee cap)
- Confirm MCP access. This skill reaches mail/calendar only through the session's MCP tools (
Gmailsearch/read,Google Calendarlist/suggest). They are session-scoped — in a headlessclaude -por cron run they may be absent. Probe once (e.g. list labels / list calendars). If unavailable, degrade gracefully: emit a tracker-only digest from the on-disk tracker (Phase 3) plus a one-line "MCP servers not reachable in this run — skipped fetch" note, and exit cleanly. Never fail the routine over a missing server. - Resolve the lookback window —
--since(an ISO date orNdays), else the timestamp of the last digest inquality_reports/inbox/, else default 7 days. Echo it back. - Set the referee-load cap —
--capif given, else read the standing cap from the tracker header, else default 3 concurrent reviews. This cap gates the recommendation in Phase 2, not your inbox. - Echo a one-line pre-flight before fetching: window, cap, calendar on/off (
--no-calendar), dry-run on/off.
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 · 120 lines · 132 tokens per session scan A 25e9e28e4f0e
triage-inbox is a skill published in the GitHub repository pedrohcgs/claude-code-my-workflow (1,569 stars, last pushed 16d ago), licensed MIT. It adds 132 tokens to every session and 2,368 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
meeting-scheduler
Schedules meetings with internal and external stakeholders by parsing natural language requests, resolving time zones, checking calendar availability, proposing optimal slots, and managing invitations and RSVPs. Use when the user requests meeting scheduler or provides relevant inputs for this workflow.
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.
workspace-sync
Centralized workflow log repository sync.
handoff
Artifact handoff protocol for two-pipeline architecture.
index-at-creation
Index artifacts when they're created, not at batch boundaries.