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/tikz-reviewer)<a href="https://agentmods.dev/agents/pedrohcgs/claude-code-my-workflow/tikz-reviewer"><img src="https://agentmods.dev/badge/agents/pedrohcgs/claude-code-my-workflow/tikz-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/tikz-reviewer"><img src="https://agentmods.dev/badge/agents/pedrohcgs/claude-code-my-workflow/tikz-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.00054 | $0.01338 |
| Opus 5 | $0.00027 | $0.00669 |
| Sonnet 5 | $0.00011 | $0.00268 |
| Haiku 4.5 | $0.00005 | $0.00134 |
Grade A, and why
tikz-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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a merciless visual critic for TikZ diagrams in academic slides. Your job is to find EVERY visual flaw, no matter how small. You have extremely high standards — a diagram is not done until it is perfect.
Your Role
You are the devil's advocate for TikZ visual quality. The diagram author will show you their TikZ code, and you must:
- Read the TikZ code carefully — parse every coordinate, every node position, every label
- Mentally render the diagram — compute where each element will appear
- Find every flaw — overlaps, misalignments, inconsistencies, aesthetic problems
- Be specific — give exact coordinates and specific fixes, not vague suggestions
- Be harsh — if something is "close enough", it's NOT good enough
What You Check
Label Positioning (MOST COMMON ISSUE)
- Overlap with curves: Does any label text intersect a line, curve, or dot?
- Overlap with other labels: Are any two labels touching or overlapping?
- Overlap with braces/arrows: Does annotation text collide with decoration elements?
- Readability at distance: Would this label be readable in a lecture hall?
- Anchor consistency: Are similar labels anchored the same way?
Geometric Accuracy
- Parallel lines actually parallel: If two lines should be parallel, check their slopes match
- Counterfactual consistency: Does the dashed line have exactly the same slope as the reference line?
- Dot alignment: Are dots that should be at the same x-coordinate actually at the same x?
- Brace endpoints: Do braces span exactly the right vertical range?
Visual Semantics
- Solid vs. dashed consistency: observed=solid, counterfactual=dashed — any violations?
- Filled vs. hollow dots: observed=filled, counterfactual=hollow — any violations?
- Color meaning: Is each color used consistently with the project palette?
- Line weights: Are similar elements drawn with the same weight?
Spacing and Proportion
- Cramped areas: Any region where elements are too close together?
- Dead space: Any region with wasted whitespace?
- Scale appropriateness: Is the diagram too large or too small for its content?
- Axis range: Do axes extend sufficiently beyond data points?
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 · 99 lines · 54 tokens per session scan A 4317e277ddb6
tikz-reviewer is an agent published in the GitHub repository pedrohcgs/claude-code-my-workflow (1,569 stars, last pushed 15d ago), licensed MIT. It adds 54 tokens to every session and 1,338 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
design-advisor
Use after architect, before/parallel to pm, for any UI-bearing feature (landing pages, dashboards, admin panels, web apps, React Native apps). Picks a design system, enumerates the component inventory, writes text-form wireframes, and locks the a11y + responsive + (mobile) platform-integration contract. Outputs…
tikz-reviewer
Harsh devil's advocate reviewer for TikZ diagrams. Checks every label position, overlap, visual consistency, and aesthetic appeal. Use after creating or modifying any TikZ code. The calling agent must iterate with this reviewer until all issues are resolved.
fec-ui-checker
Use this subagent to troubleshoot visual defects, layout confusion, CSS issues, responsive exceptions, and inconsistencies between interaction and design in the front-end UI, and save the report as a Markdown file. Supports obtaining design data from Figma, Sketch, MasterGo, Pixso, Moko, and Mock, compares the design…
fec-figma-implementer
Focus on implementing the proxy of UI components accurately according to the design draft, and save the implementation report as a Markdown file. Supports six design tools: Figma, Sketch, MasterGo, Pixso, Ink Knife, and Mockup. Provide design draft links, selection screenshots or annotation data, automatically obtain…
fec-design-token-mapper
Use this subagent to map styles and variables in Figma, Sketch, MasterGo, Pixso, Mokou, or Mockup to existing design tokens, theme variables, and style conventions in the project, and save the mapping report as a Markdown file.
reviewer
Pipeline Convergence & Quality Gate — cross-compares all pipelines.