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 instructions/cybertronai/sutroyaro/agents-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/agents-md)<a href="https://agentmods.dev/instructions/cybertronai/sutroyaro/agents-md"><img src="https://agentmods.dev/badge/instructions/cybertronai/sutroyaro/agents-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 | $0.01014 | $0.01014 |
| Opus 5 | $0.00507 | $0.00507 |
| Sonnet 5 | $0.00203 | $0.00203 |
| Haiku 4.5 | $0.00101 | $0.00101 |
Grade A, and why
SutroYaro AGENTS.md 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 4d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This project uses AI agents (Claude Code, Codex CLI, Gemini CLI, Replit, others) for research and accepts contributions from both humans and agents.
For single agents (getting started)
If you are the only agent working on this project, read these in order:
- CLAUDE.md - Deep technical context: project goals, metrics (ARD/DMC), best methods, 36 experiments, current state
- DISCOVERIES.md - Knowledge base: proven facts, failed approaches, open questions (Q7, Q11-Q13)
- LAB.md - Experiment protocol: templates, lifecycle, baselines, rules
- AGENT.md (optional) - Only if running autonomous overnight loops
Note: CLAUDE.md is the canonical technical source regardless of which model/tool you use (Claude, Gemini, Kimi, etc.).
How AI agents were used
Phase 1 (16 experiments): Single Claude Code sessions running experiments sequentially, each following the template in src/sparse_parity/experiments/_template.py.
Phase 2 (17 experiments): 17 independent Claude Code agents dispatched in parallel, each implementing a different algorithmic approach to sparse parity. Each agent received the approach description, shared module APIs, three test configs, and a findings template. All 17 completed successfully, producing code, results, and findings.
Survey: A single agent wrote the Practitioner's Field Guide (docs/research/survey.md) synthesizing all 33 experiments, with spec compliance and code quality review passes.
Meeting #8 onward: Multiple group members run their own agent harnesses (Germain's Replit Research OS, Michael's Claude approach, Yaroslav's Gemini). Results flow in via PRs and the contributions/ directory.
For agents reviewing PRs
When reviewing a contributed experiment:
- Check that the experiment ran (results.json should match the findings doc)
- Check DISCOVERIES.md for prior work on the same question
- Verify the contributor didn't modify measurement code (tracker.py, cache_tracker.py, data.py, config.py)
- If the experiment answers an open question, check that DISCOVERIES.md is updated
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.
- 4d ago First seen · 72 lines · 1,014 tokens per session scan A b133210b92ae
SutroYaro AGENTS.md is an instructions file published in the GitHub repository cybertronai/SutroYaro (16 stars, last pushed 3mo ago), licensed Unlicense. It adds 1,014 tokens to every session, about $0.0051 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 instructions, from other repositories
PINA AGENTS.md
AGENTS.md instructions for PINA-org/PINA, covering pina — physics-informed neural architectures, quick reference, workflow: problem → model → solver → trainer, problem types and condition types.
ClimaAtmos.jl AGENTS.md
Instructions for CliMA/ClimaAtmos.jl, covering climaatmos agent guide, ecosystem guidelines, repo-specific guidelines, local norms and self-correction.
tpu_performance_autoresearch_wiki GEMINI.md
Instructions for vlasenkoalexey/tpu_performance_autoresearch_wiki, covering gemini/antigravity operating rules, platform adaptation (claude code → gemini/antigravity), 1. skills — native, no emulation, 2. never-stop hook & retrospectives and 3. session and transcript resolution.
co-mathematician CLAUDE.md
Instructions for VeryMath/co-mathematician, covering claude.md, repository contract, required flow, claude code operating notes and harness commands.
tpu_performance_autoresearch_wiki CLAUDE.md
Instructions for vlasenkoalexey/tpu_performance_autoresearch_wiki, a project described as: Wiki built using Karpathy method containing information about TPU performance optimizations and hooking it up to autoresearch optimization engine.
HumanoidClimb-RL CLAUDE.md
Instructions for s1ddh-rth/HumanoidClimb-RL, covering claude.md, environment setup, common commands, architecture and data flow.