agentleFS
cybertronaicybertronai/SutroYaro/.codex/AGENTS.md

SutroYaro

AGENTS.md16 starsChanged 6 months agoUnlicenseView on GitHub

These instructions apply to all Codex CLI sessions in this repo. Load current project state before running experiments, reviewing PRs, or writing findings. If telegram.db is missing or stale, run bin/tg-sync. Run at session start and before any push: Before pushing: 1. Update docs/changelog.md (bump version) 2. python3 -m mkdocs build to verify no broken links 3. Show the diff and wait for approval before git push Apply these to all prose (findings docs, DISCOVERIES.md updates, PR descriptions): Full guide:…

  • Commits and pushes
  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 33,315 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository9 other files it gives its agents.

The file

We split this AGENTS.md into the rules it gives an agent

11 rules. About 0 are common, 9 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read these files in order:

    line 9
  2. Distinctive:

    Check recent Telegram activity (if synced):

    line 15
  3. Very specific:

    If telegram.db is missing or stale, run bin/tg-sync.

    line 22
  4. Distinctive:

    Check GitHub for open work:

    line 24
  5. Distinctive:

    Before writing code, check:

    line 31
  6. Distinctive:

    Run at session start and before any push:

    line 49
  7. Very specific:

    Update docs/changelog.md (bump version)

    line 70
  8. Distinctive:

    Prefer plain verbs. "used" not "leveraged," "showed" not "showcased."

    line 82
  9. Distinctive:

    Use simple copulatives. Write "X is Y" not "X serves as Y."

    line 83
  10. Distinctive:

    Never triple. Two items in a list, not three.

    line 85
  11. Distinctive:

    No AI vocabulary: delve, tapestry, landscape, pivotal, showcase, testament, underscore, foster, garner, interplay, intricate, vibrant, …

    line 87

≈ “Common” is an estimate: at least 1 in 5 of the 42,283 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

Codex Project Instructions

These instructions apply to all Codex CLI sessions in this repo.

Before Any Research Task

Load current project state before running experiments, reviewing PRs, or writing findings.

  1. Read these files in order:
    • CODEX.md -- project context, current best methods, constraints
    • DISCOVERIES.md -- what's proven, what failed, open questions (bottom of file)
    • AGENT.md -- machine-executable experiment loop (if running autonomous)
    • LAB.md -- experiment protocol, rules (especially rule #9: metric isolation)
  2. Check recent Telegram activity (if synced):
test -f telegram.db && sqlite3 telegram.db \
  "SELECT date, sender, text FROM messages ORDER BY date DESC LIMIT 10;"

If telegram.db is missing or stale, run bin/tg-sync.

  1. Check GitHub for open work:
gh pr list --repo cybertronai/SutroYaro --state open
gh issue list --repo cybertronai/SutroYaro --state open
  1. Before writing code, check:
    • research/search_space.yaml for allowed parameter ranges
    • research/questions.yaml for the dependency graph of open questions

Current State

FactValue
Fastest historical methodGF(2) Gaussian elimination, 509us, ARD ~420
Primary energy metricByteDMD, byte-granularity LRU stack cost
Legacy metricsARD and DMC values remain useful for historical comparisons
Experiments done37+ (see research/log.jsonl and docs/research/survey.md)
Open questionsBottom of DISCOVERIES.md
Next milestoneByteDMD-aware sparse parity and nanoGPT experiments
Meeting cadenceMondays 18:00 at South Park Commons

Sync Routine

Run at session start and before any push:

# Telegram (daily, incremental SQLite sync)
bin/tg-sync

# Query recent messages
sqlite3 telegram.db "SELECT date, sender, text FROM messages ORDER BY date DESC LIMIT 10"

# Post status updates when configured
bin/tg-post --topic agent-updates "Status update"

# Google Docs (weekly, after Monday meetings)
python3 src/sync_google_docs.py

# GitHub
gh pr list --repo cybertronai/SutroYaro --state open
gh issue list --repo cybertronai/SutroYaro --state open

Before pushing:

  1. Update docs/changelog.md (bump version)
  2. python3 -m mkdocs build to verify no broken links
  3. Show the diff and wait for approval before git push

Writing Rules (Anti-Slop)

Apply these to all prose (findings docs, DISCOVERIES.md updates, PR descriptions):

  1. Cut filler phrases. Say the thing directly.
  2. Break formulaic structures. No binary contrasts, no dramatic fragmentation.
  3. Vary rhythm. Mix sentence lengths. Two items beat three.
  4. Trust readers. State facts directly.
  5. Prefer plain verbs. "used" not "leveraged," "showed" not "showcased."
  6. Use simple copulatives. Write "X is Y" not "X serves as Y."
  7. Kill em dashes. Use commas or periods.
  8. Never triple. Two items in a list, not three.
  9. Be specific. Replace generic statements with concrete details.
  10. No AI vocabulary: delve, tapestry, landscape, pivotal, showcase, testament, underscore, foster, garner, interplay, intricate, vibrant, robust, seamless, paramount, multifaceted, nuanced, groundbreaking, cornerstone, transformative, synergy.

Full guide: .claude/skills/anti-slop-guide/SKILL.md (plain markdown, readable by any tool).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.