agentleFS
Sign inStart free
tikocitikoci/rosetta/AGENTS.md

rosetta

AGENTS.md54 starsChanged 4 months agoMITView on GitHub

Codex reads this file as the repo-local entrypoint. Keep it short. The canonical project orientation remains CLAUDE.md; durable rationale lives in DESIGN.md; operator/reference material lives in MANUAL.md; narrow normative rules live in .github/instructions/*.instructions.md. - Read CLAUDE.md before non-trivial work. It is the routing index for the repo. - Read DESIGN.md when touching retrieval, MCP/TUI behavior, data sources, extraction, skills, command validation, or Docusaurus migration work. - Read .github/copilot-instructions.md as the peer short routing note for Copilot, but do not duplicate…

  • 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 31,542 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 repository8 other files it gives its agents.

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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 CLAUDE.md before non-trivial work.

    line 10
  2. Very specific:

    Read DESIGN.md when touching retrieval, MCP/TUI behavior, data sources, extraction, skills, command validation, or Docusaurus migration …

    line 11
  3. Very specific:

    Read .github/copilot-instructions.md as the peer short routing note for Copilot, but do not duplicate its rules here.

    line 13
  4. Distinctive:

    If setup output changes, keep the runtime snippets, README, and MANUAL aligned.

    line 45

≈ “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

Codex instructions for rosetta

Codex reads this file as the repo-local entrypoint. Keep it short. The canonical project orientation remains CLAUDE.md; durable rationale lives in DESIGN.md; operator/reference material lives in MANUAL.md; narrow normative rules live in .github/instructions/*.instructions.md.

First reads

  • Read CLAUDE.md before non-trivial work. It is the routing index for the repo.
  • Read DESIGN.md when touching retrieval, MCP/TUI behavior, data sources, extraction, skills, command validation, or Docusaurus migration work.
  • Read .github/copilot-instructions.md as the peer short routing note for Copilot, but do not duplicate its rules here.
  • Manually read the matching .github/instructions/*.instructions.md files. Codex does not get Copilot's applyTo selection automatically.
  • Active work is tracked in GitHub Issues (agent-ready / umbrella / blocked labels); PRs close issues via Closes #N — read .github/instructions/issue-pr-linking.instructions.md. tasks/ is a frozen archive (see tasks/README.md); briefing rules are in briefings/README.md.
  • Repo-local skills live in .github/skills/*/SKILL.md (symlinked into .claude/skills/ for Claude Code); read the relevant file when a user asks for that workflow, such as picking the next issue, promoting an idea, re-extracting, verifying acceptance criteria, or gating a PR's review threads before claiming it's mergeable.

Development defaults

  • Rosetta is Bun + TypeScript. Prefer bun, bun test, and make verify where applicable; do not swap in Node/npm-oriented substitutes.
  • MCP, query, classifier, TUI, and canonicalizer behavior should route through shared core code, usually src/query.ts, with src/mcp.ts and src/browse.ts kept as thin adapters.
  • Rosetta is read-only documentation/schema context. It does not connect to or modify a user's router.
  • Community RouterOS skills are supplemental, not official MikroTik docs; keep the attribution boundary visible when they surface.

MCP and client config

  • Dev MCP config for Claude-style clients is in .mcp.json.
  • VS Code Copilot MCP config is in .vscode/mcp.json.
  • Public client setup snippets live in README.md and src/setup.ts, including the Codex command codex mcp add rosetta -- bunx @tikoci/rosetta.
  • If setup output changes, keep the runtime snippets, README, and MANUAL aligned.

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.

Check your setup, free