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 agentmods add commands/zayne-sprague/dr-claude-code/find-computegit clone --depth 1 https://github.com/Zayne-sprague/Dr-Claude-CodeWrote 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/commands/zayne-sprague/dr-claude-code/find-compute)<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="Measured on agentmods" 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 | $0.00034 | $0.01182 |
| Opus 5 | $0.00017 | $0.00591 |
| Sonnet 5 | $0.00007 | $0.00236 |
| Haiku 4.5 | $0.00003 | $0.00118 |
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 3d 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 — 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"
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.
- 3d ago First seen · 123 lines · 34 tokens per session scan A c304d1f6f284
find-compute is a command published in the GitHub repository Zayne-sprague/Dr-Claude-Code (5 stars, last pushed 5mo ago), licensed MIT. It adds 34 tokens to every session and 1,182 once invoked, about $0.0002 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-31.
Other commands, from other repositories
check-dev
Type-check a Z specification with fuzz.
me-figure-discussion
Write or review thermal-fluid figure discussion with observation, physical mechanism, comparison, uncertainty, and claim limits.
master_analysis
Run comprehensive 5-phase analysis across labs, genetics, and protocols.
run-panguweather
Guide the user through running PanguWeather end-to-end on an AMD cluster.
render-figures
Compile all .tex and .typ figure files in a directory.
diff
Quantitative volume comparison between a CadQuery model and a reference STEP file.