agentleFS
DaeSeokSongDaeSeokSong/oh-my-ouroboros/AGENTS.md

oh-my-ouroboros

AGENTS.md3 starsChanged 4 months agoMITView on GitHub

13 specialized agents with defined roles, models, tools, and routing triggers. Note: For /discuss sessions any agent may be summoned as a teammate (SendMessage-capable) via TeamCreate — researcher is the most common, but architecture debates summon planner/coder etc. (see canonical examples in rules/agent-routing.md). Outside discussions, all run subagent-only.

The file

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

7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Constraints: Always called by other agents — never directly performs code edits

    line 33
  2. Distinctive:

    Special: All agents may freely summon searcher for search sub-tasks

    line 34
  3. Distinctive:

    Constraints: No execution — writes to file only.

    line 51
  4. Distinctive:

    Refactor guard: No refactoring during active experiments

    line 53
  5. Distinctive:

    Trigger: After code changes, test execution, "검증해", "테스트해"

    line 56
  6. Very specific:

    Output: Commit message following {issue} {type}: {Subject} format

    line 81
  7. Distinctive:

    Exit: all questions answered correctly (+ integration check), or user stops, or an item stuck at ladder rung 6 is handed off as "tutor …

    line 93

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 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

Agent Catalog

13 specialized agents with defined roles, models, tools, and routing triggers.


Agent Table

AgentModelRoleCore ToolsInvocation
searcherSonnetInternet search — papers, library docs, tech articlesTavily MCP, WebSearch, WebFetchsubagent
scoutHaikuCodebase recon + project structure analysis (deepinit mode)Glob, Grep, Read, Bash(read-only)subagent
plannerOpusArchitecture design, experiment planning, workflowRead, Glob, Grepsubagent
coderSonnetCode write/modify/review + conditional refactorRead, Write, Edit, Bashsubagent
qaSonnetValidation, test execution, bug tracing (tracer mode), Ralph loopRead, Grep, Glob, Bash, Edit(FAIL fixes · paper-read qa-report.md only)subagent
securitySonnetCode vulnerability review — injection/authz/secret exposure/supply chain (4 lenses), /security-review + claude-security plugin liaisonRead, Grep, Glob, Bashsubagent
reviewerOpusOne-function-at-a-time DFS code review — gaps between design intent and code (unjustified constants, comment/code mismatch, unreachable branches, deviation from design docs); method in rules-lazy/code-review-dfs.mdRead, Grep, Glob, Bashsubagent
researcherOpusPaper writing, experiment analysis, critical design evaluationRead, Write, Editsubagent / teammate
designerSonnetFigures, TikZ diagrams, matplotlib plotsRead, Write, Edit, Bashsubagent
docsSonnetConfluence pages, Jira issues, documentationRead, Write, Edit, MCPsubagent
gitopsSonnetGit commit, branch, diff, log, stashBash(git), Readsubagent
citation-verifierSonnetCitation trust verification — retraction/correction detection + stance debate (scite replacement)WebFetch, WebSearch, scientific-papers/arxiv-latex/tavily MCPsubagent
tutorOpusUser-comprehension teacher — quiz → misconception diagnosis → step-down re-explanation → re-quiz until all correct (an item exhausted at ladder rung 6 is handed off as "tutor limit" and excluded); external material only via searcher (NEEDS_SEARCH)Read, Grep, Glob, Write/Edit (quiz.md·quiz-key.md·primer.md·math-notes.md in the artifact folder only; quiz-search.log·quiz-visual.log·artifact-log.tsv·artifact/study.html are main-only)subagent (main relays rounds via SendMessage)

Note: For /discuss sessions any agent may be summoned as a teammate (SendMessage-capable) via TeamCreate — researcher is the most common, but architecture debates summon planner/coder etc. (see canonical examples in rules/agent-routing.md). Outside discussions, all run subagent-only.


Agent Detail

searcher

  • Trigger: "검색해", "찾아봐", internet resource needed, paper lookup
  • Constraints: Always called by other agents — never directly performs code edits
  • Special: All agents may freely summon searcher for search sub-tasks
  • Tavily: Uses search for general queries, extract for full-page content

scout

  • Trigger: "파일 찾아", "코드 어디", project structure unknown, before coder/qa
  • Modes:
    • Standard: symbol/file search via Glob + Grep
    • deepinit: full project structure analysis for new projects
  • Output: File list + dependency graph + impact scope

planner

  • Trigger: Architecture design, experiment planning, "설계해", workflow creation
  • Constraints: Delegates all search to searcher; no direct internet access
  • Output: Phase plan with gate conditions, team composition, artifact list

coder

  • Trigger: Code write, modify, bug fix, new module
  • Constraints: No execution — writes to file only; user runs
  • Special: Calls scout before writing to understand impact scope
  • Refactor guard: No refactoring during active experiments

qa

  • Trigger: After code changes, test execution, "검증해", "테스트해"
  • Modes:
    • Standard: syntax/import check, test run, PASS/FAIL report
    • tracer: causal bug tracing — follows call chain to root cause
    • ralph-loop: auto-retry loop until tests pass (5-Gate guarded)
  • Ralph Wiggum Loop: Max N retry rounds; escalates to main on convergence failure

researcher

  • Trigger: Paper writing, experiment analysis, "논문", "비교 분석", critical evaluation
  • Teammate mode: Participates in /discuss sessions with SendMessage
  • Constraints: Delegates search to searcher; does not execute code

designer

  • Trigger: Figure generation, TikZ diagrams, matplotlib plots, "그림 그려", "시각화"
  • Standards: TikZ for structural diagrams; matplotlib for data plots
  • Output: Saved to docs/paper/figures/ (or project-specified path)

docs

  • Trigger: Confluence page create/update, Jira issue, "문서화", "컨플루언스"
  • Protocol: 3-step confirmation before any Confluence update (see CLAUDE.md)
  • MCP: Uses Confluence MCP + Jira MCP; Jira comments only via scripts/jira_comment.py (preview → user approval → post·update), never the MCP comment tool

gitops

  • Trigger: "커밋해", "브랜치", "diff", "로그", git operations
  • Constraints: push/pull are user-only — gitops only handles local git ops
  • Output: Commit message following {issue} {type}: {Subject} format

citation-verifier

  • Trigger: right before citing a paper in text/experiments; SOTA baseline or domain-mechanism references; pre-2020 citations (routing 3.6)
  • Modes: advocate + skeptic in parallel → synthesis debate; retraction gate (Crossref + OpenAlex) runs first
  • Constraints: returns verdict only — no file writes (untrusted isolation); caller (main) stores results (mem0 T21 + detail log per rules-lazy/citation-verification-log.md)
  • Verdict: 허용 / 경고 / 금지 with supporting/contrasting/mentioning counts and confidence

tutor

  • Trigger: "이해 안 돼", "다시 설명해줘", "퀴즈 내줘", "가르쳐줘" on an existing artifact; /paper-read Step 7 and /research close-out after conclusions are confirmed by the key-paper deep read (mandatory); /discuss and /experiment reports (offered)
  • Modes: quiz / diagnose (misconception type: term·formula·causality·number·context) / reteach (explanation ladder, one rung lower per round) / verify (re-quiz wrong items only) / explain (math·science concept note + ELI5 Q&A, no quiz)
  • Constraints: no web access — emits NEEDS_SEARCH, main runs searcher and feeds back the summary; writes only quiz.md (questions, round log) and quiz-key.md (answers, opened by main only at grading); questions and answers must be grounded in the artifact (notes/review) — external material is auxiliary and labeled
  • Exit: all questions answered correctly (+ integration check), or user stops, or an item stuck at ladder rung 6 is handed off as "tutor limit" and excluded from the loop; main records rounds and final score in Mem0

Routing Priority

Canonical: rules/agent-routing.md § 라우팅 테이블 (24 rows, first-match wins). The table below is a condensed mirror for quick lookup — on any conflict the canonical file wins, and edits must land there first.

PriorityTriggerPrimary AgentSecondary
0.52+ independent tasks (paper reviews always go to 3.5)parallel-dispatchqa/coder/scout/searcher
0.7Repeat/monitor pattern/loop skillralph-loop (qa)
1Code modify/writescout → coderqa ∥ security
1.9Branch/module full code review, "파고들어", design-intent comparison (narrower than row 2, so above it)reviewer (reads rules-lazy/code-review-dfs.md first, returns one function at a time)main Q&A/records, user decides, coder applies in bulk
2Code review/validatescout → qa ∥ securitycoder
2.5Bug root causescout → qa (tracer) ∥ securitycoder
2.6New project structurescout (deepinit)—
2.7Security review/vulnerability checksecurity/security-review (light) · claude-security plugin (deep, depth gate)
3Internet search (paper/arXiv keywords → 3.5 wins, narrower trigger)searcherresearcher
3.5Paper search/read (any number of papers)/paper-read skillsearcher → citation-verifier → scout → main(triage) → researcher×3 → qa → docs → tutor
3.6Citation trust check (pre-citation)citation-verifiersearcher
3.7Deep multi-source research/research skillsearcher/citation-verifier/researcher → tutor (close-out, mandatory)
3.75Follow-up question on the previous report's math/science note, or a concept that needs a formulatutor explain (mandatory; math-notes.md + ELI5 Q&A, no quiz; spawn prompt names mode=explain)designer (NEEDS_VISUAL) · searcher (NEEDS_SEARCH, return-only) · continue to a quiz only after user accepts, via 3.8
3.8Comprehension help on an existing artifact ("이해 안 돼", "퀴즈 내줘"), paper-read Step 7, research close-out (after key-paper deep read confirms conclusions)tutor (via main, after main confirms artifact type: paper review / research report / experiment report / none)searcher (NEEDS_SEARCH, max 3 per artifact, main counts via quiz-search.log) · if none, ask the type; papers → /paper-read sequentially first; experiment reports proceed directly
4File/symbol searchscout—
4.85Start of a non-trivial task (experiment, feature, harness feat:), "의뢰서", "왜 하는지부터"/intent skill (write intent.md → user correction → commit; approval triggers the plan)superpowers:writing-plans (plan.md) · 4.9 brainstorming comes after intent
4.9New feature/system design (pre-implementation)brainstorming opt-inplanner/coder
5Architecture/experimentplannerresearcher
6Paper write/analysisresearchersearcher
7Figure/diagramdesignerresearcher
8Confluence/Jiradocs—
8.5Git operationsgitops—
9Discussion/debateTeamCreate → teammates/discuss skill
10Simple Q&Amain direct—

Invocation Modes

Subagent (Single Task)

Agent(subagent_type="coder", description="sonnet: Modify loss function")

Teammate (Discussion)

TeamCreate(team_name="arch-review")
Agent(team_name="arch-review", name="researcher", ...)
Agent(team_name="arch-review", name="planner", ...)

Teammates use SendMessage for cross-agent communication. Required for /discuss sessions.


Skill Auto-Call (4-Gate)

Agents may autonomously invoke whitelisted skills after passing all 4 gates:

GateCondition
1Skill is in agent's whitelist (agents/*.md)
2Task cannot complete without skill
3Quality threshold unmet without skill
4Context < 60%

SKILL_DEPTH=1 in spawn prompt disables all skill auto-calls (recursion guard).

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.