claude-sisyphus-grad: Command for Claude Code

.claude/commands/analyze.md

analyze is a command for Claude Code from Hwiyeon/claude-sisyphus-grad. It costs 0 tokens per session (716 once invoked), scanned A, original, MIT.

A command that reviews a machine-learning training script and its configuration through a briefing, several agent discussions, and a judging step. It can optionally apply the chosen code change on a new branch.

In plain words
What is it for?
Use it to analyze a training script and configuration, repeat review cycles, generate reports in a chosen language, and optionally apply the review decision.
Why use it?
It gathers several review stages before changing training code, making the proposed next action explicit. It also checks that the required script and configuration files exist.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions CLAUDE.md.

This is Hwiyeon/claude-sisyphus-grad's own configuration. It tells Claude Code how to work on claude-sisyphus-grad itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claude-sisyphus-grad configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Hwiyeon/claude-sisyphus-grad. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Hwiyeon/claude-sisyphus-grad/main/.claude/commands/analyze.md
Clone the repo
git clone --depth 1 https://github.com/Hwiyeon/claude-sisyphus-grad

Made for: Claude Code.

Wrote 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.

agentmods badge for analyze

README.md
[![agentmods](https://agentmods.dev/badge/commands/hwiyeon/claude-sisyphus-grad/analyze/github.svg)](https://agentmods.dev/commands/hwiyeon/claude-sisyphus-grad/analyze)
Your own site
<a href="https://agentmods.dev/commands/hwiyeon/claude-sisyphus-grad/analyze"><img src="https://agentmods.dev/badge/commands/hwiyeon/claude-sisyphus-grad/analyze/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.

agentmods 80×15 button for analyze

Your own site · 80×15
<a href="https://agentmods.dev/commands/hwiyeon/claude-sisyphus-grad/analyze"><img src="https://agentmods.dev/badge/commands/hwiyeon/claude-sisyphus-grad/analyze.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 716 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00716
Opus 5 $0.00000 $0.00358
Sonnet 5 $0.00000 $0.00143
Haiku 4.5 $0.00000 $0.00072

Measured 12d ago against content hash ef98d573ad38, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

analyze 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 12d 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.

.claude/commands/analyze.md · 89 lines

How it starts

The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Standalone Pre-Analysis Command

Runs a Briefing + multi-agent discussion on the training script and config, and optionally applies improvements automatically via a Code Modifier. This is a command that runs the analyze mode of /train independently.


Usage

/analyze script=train.py config=configs/config.yaml [review_cycles=1] [apply=true] [branch_name=analyze-mod]

Arguments

argument description default
script path to the training script to analyze required
config path to the config file to analyze required
review_cycles number of G→round2→round3→Judge cycle repetitions 1
apply whether to automatically apply the Judge decision's NEXT_ACTION true
branch_name branch name to create when modifying code analyze-mod

| lang | output language for reports and messages (ko, en, etc.). The project's CLAUDE.md defines the default | project default |


Procedure

Step 1: Parse and Validate Arguments

Parse arguments from $ARGUMENTS.

  • Verify that script and config files exist
  • Print parsed values for user confirmation

Step 2: Create Output Directory

research/logs/{YYYY-MM-DD}/analyze_{HH-MM}/
├── reports/
│   ├── pre_analysis_briefing.md
│   └── pre_review_discussion.md
└── cache/

Step 3: Load Modules

Read the following two files to load rules:

  • .claude/prompts/train-recording-rules.md (Briefing agent, pre-review discussion format)
  • .claude/prompts/train-review-pipeline.md (multi-agent review discussion)

Step 4: Call Briefing Agent

Call Briefing agent per the "Pre-Analysis and Model Improvement" section of train-recording-rules.md:

  • Input: eval_results/, research/logs/, research/README.md, {script}, {config}
  • Output: reports/pre_analysis_briefing.md

Step 5: Multi-Agent Analysis Discussion

Run multi-agent discussion per train-review-pipeline.md rules:

  • Discussion content recorded in reports/pre_review_discussion.md
  • Discussion topics: performance bottlenecks, config vs. structural changes, specific improvements, risks/expected impact

Read the full file on GitHub · 89 lines

Changes

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.

  1. 12d ago First seen · 89 lines · 0 tokens per session scan A ef98d573ad38

Subscribe to this mod's changes

analyze is a command published in the GitHub repository Hwiyeon/claude-sisyphus-grad (59 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 716 tokens. 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.