Dr-Claude-Code: Command for Claude Code

.claude/commands/raca/find-compute.md

find-compute is a command for Claude Code from Zayne-sprague/Dr-Claude-Code. It costs 34 tokens per session (1,182 once invoked), scanned A, original, MIT.

A command that compares configured computing clusters to find a suitable place to run a job. It reads cluster settings, checks queues and access, and estimates cost.

In plain words
What is it for?
It compares local, Slurm, and RunPod clusters for training, inference, or evaluation jobs based on GPU needs and expected runtime.
Why use it?
It reduces the manual work of deciding where a job should run and shows when a cluster is unavailable or inaccessible.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: positional $N argument.

This is Zayne-sprague/Dr-Claude-Code's own configuration. It tells Claude Code how to work on Dr-Claude-Code 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 Dr-Claude-Code configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Zayne-sprague/Dr-Claude-Code. 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/Zayne-sprague/Dr-Claude-Code/main/.claude/commands/raca/find-compute.md
Clone the repo
git clone --depth 1 https://github.com/Zayne-sprague/Dr-Claude-Code

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 find-compute

README.md
[![agentmods](https://agentmods.dev/badge/commands/zayne-sprague/dr-claude-code/find-compute/github.svg)](https://agentmods.dev/commands/zayne-sprague/dr-claude-code/find-compute)
Your own site
<a href="https://agentmods.dev/commands/zayne-sprague/dr-claude-code/find-compute"><img src="https://agentmods.dev/badge/commands/zayne-sprague/dr-claude-code/find-compute/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 find-compute

Your own site · 80×15
<a href="https://agentmods.dev/commands/zayne-sprague/dr-claude-code/find-compute"><img src="https://agentmods.dev/badge/commands/zayne-sprague/dr-claude-code/find-compute.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,182 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.00034 $0.01182
Opus 5.5 $0.00014 $0.00473
Sonnet 5.5 $0.00007 $0.00236
Haiku 4.5 $0.00003 $0.00118

Measured 2mo ago against content hash c304d1f6f284, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

find-compute 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 2mo 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/raca/find-compute.md · 123 lines

How it starts

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

Find Compute

Find the best place to run a job across all configured compute in .raca/clusters.yaml.

Step 1: Read the cluster config

cat .raca/clusters.yaml

Extract all configured clusters. For each, note:

  • type (slurm / runpod / local)
  • GPU types and VRAM
  • For SLURM: partitions and accounts available

Step 2: Parse arguments

From the command arguments, extract:

  • --gpus N — number of GPUs needed (default: 1)
  • --time Xh — estimated job duration (default: unknown)
  • --job-type — training, inference, or eval (for cost/capability reasoning)

Step 3: Check each cluster

For SLURM clusters

For each configured SLURM cluster, run these checks via raca ssh:

# Check queue status — what's running and pending
raca ssh <cluster> "squeue --format='%P %T %G %M %l' --noheader | head -30"

# Check partition availability
raca ssh <cluster> "sinfo --format='%P %G %D %a %t' --noheader"

# Verify actual access with sbatch --test-only
raca ssh <cluster> "sbatch --test-only --partition=<partition> <gpu_directive> --account=<account> --time=00:05:00 --wrap='hostname' 2>&1"

If raca ssh fails (VPN, auth), note the cluster as "unreachable" — do not skip it silently.

From the queue output, estimate wait time:

  • 0 jobs in partition → idle (minutes)
  • 1-5 jobs → minutes to hours
  • 6-20 jobs → hours
  • 20+ jobs → days — flag as congested

For RunPod

Check if the API key is available:

echo ${RUNPOD_API_KEY:+set}

If set, estimate cost:

hourly_cost = GPU_cost_per_hour (from .raca/clusters.yaml or reference table)
total_cost = hourly_cost × estimated_hours × gpu_count

RunPod GPU pricing reference (community cloud, approximate):

GPU $/hr
H200 SXM ~$3.49
H100 SXM ~$2.49
A100 SXM ~$1.64
L40S ~$0.99
RTX 4090 ~$0.44
RTX 3090 ~$0.22

Note: RunPod has no queue wait — pods start in ~1-3 minutes.

For local

nvidia-smi --query-gpu=name,memory.total,utilization.gpu --format=csv,noheader 2>/dev/null \
  || system_profiler SPDisplaysDataType 2>/dev/null | grep -E "Chipset|VRAM"

Read the full file on GitHub · 123 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. 2mo ago First seen · 123 lines · 34 tokens per session scan A c304d1f6f284

Subscribe to this mod's changes

find-compute is a command published in the GitHub repository Zayne-sprague/Dr-Claude-Code (5 stars, last pushed 7mo ago), licensed MIT. It adds 34 tokens to every session and 1,182 once invoked, about $0.0001 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-31.

Related

find-compute compared with commands from other repositories

find-compute next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
find-computeZayne-sprague/Dr-Claude-CodeCommand57mo agoMITA34Claude Code
verify-mathflonat/flonat-researchCommand1493d agoMITA81Claude Code
difffa-mc/vibe-cadingCommand824d agoAGPL-3.0A14Claude Code
arg-diagramMasqiller/ARG-RESEARCHER-V4.1Command65mo agoMITA14Claude Code
plotzhouziyue233/great-econometricsCommand86mo agononeA44Claude Code
graphite-morphology-classifyDaxxSec/cognitropy-labCommand14mo agononeA0Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code