Borrowing it
Nothing to install: this file belongs to cybertronai/SutroYaro. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/cybertronai/SutroYaro/main/CLAUDE.mdgit clone --depth 1 https://github.com/cybertronai/SutroYaroWrote 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/instructions/cybertronai/sutroyaro/claude-md)<a href="https://agentmods.dev/instructions/cybertronai/sutroyaro/claude-md"><img src="https://agentmods.dev/badge/instructions/cybertronai/sutroyaro/claude-md.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.1 | $0.03923 | $0.03923 |
| Opus 5 | $0.01962 | $0.01962 |
| Sonnet 5 | $0.00785 | $0.00785 |
| Haiku 4.5 | $0.00392 | $0.00392 |
Grade C, and why
SutroYaro CLAUDE.md scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl --proto '=https' --tlsv1.2 -sSf https://install.determinate.systems/nix | sh -s -- install Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl --proto '=https' --tlsv1.2 -sSf https://install.determinate.systems/nix | sh -s -- install How it starts
The opening of the file, as written. The whole thing — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md - Sutro Group Research Workspace
Project Context
This is a research workspace for the Sutro Group, a study group exploring energy-efficient AI training. The group meets weekly at South Park Commons in San Francisco.
Scoped role of this repo (read this first)
SutroYaro is the lab's memory and dispatcher — not the research front, not the metric, not the benchmark problems. Five things it does:
- Lab memory —
DISCOVERIES.mdis the curated "what's proven" record. New agents read this BEFORE running experiments to avoid spending tokens on settled work. - Agent-teams dispatcher — the patterns in
.claude/skills/,bin/, hooks, and theagent-teamsmachinery here are how new builds (e.g. hinton-problems, schmidhuber-problems) get launched. - Cross-repo index —
docs/related-repos.mdis the curated map of the 8-repo cybertronai org. - Public face —
docs/+ mkdocs build the site shown at Monday meetings. - Telegram + Google Docs + GitHub sync —
bin/tg-sync,src/sync_google_docs.py, daily catchups.
What this repo is NOT (so you don't accidentally do work in the wrong place):
- NOT the active research front. That's at
cybertronai/ByteDMD/experiments/grid(Yaroslav) andcybertronai/simplified-dally-model(Yaroslav, 2D grid cost model). - NOT the home for benchmark problems. Those are in dedicated repos:
sparse-parity-challenge,hinton-problems,schmidhuber-problems,sutro-problems. - NOT the cost metric definition. That's in
ByteDMDandsimplified-dally-model.
If you're about to write experiment code or a new benchmark stub here, stop and check whether one of the per-purpose repos is the right home. SutroYaro should accumulate findings, not source code that belongs elsewhere. A reshuffle to align the codebase with this scoped role is tracked as a meta issue.
Read These First
- docs/challenges.md — The four-challenge index: what each challenge is, where it lives, current state
- LAB.md — Protocol for running experiments (templates, lifecycle, rules)
- AGENT.md — Machine-executable experiment loop for autonomous sessions
- DISCOVERIES.md — What's proven so far (read before every experiment)
- CONTRIBUTING.md — How external contributors submit experiments and findings
- TODO.md — Open research tasks
- docs/tasks/INDEX.md — Current task tracker with priorities
- docs/research/survey.md — Practitioner's Field Guide ranking all 37 experiments
- docs/research/peer-research-protocol.md — Full design doc for multi-researcher autonomous research
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 · 233 lines · 3,923 tokens per session scan C 1b20cfa3b67b
SutroYaro CLAUDE.md is an instructions file published in the GitHub repository cybertronai/SutroYaro (16 stars, last pushed 3mo ago), licensed Unlicense. It adds 3,923 tokens to every session, about $0.0196 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.