agentleFS
Sign inStart free
MrZarrarMrZarrar/Jarvis-Sub-Agent-Dashboard/AGENTS.md

Jarvis-Sub-Agent-Dashboard

AGENTS.md0 starsChanged 4 months agoMITView on GitHub

The file

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

6 rules. About 0 are common, 6 are distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep this repository a stable, local-first Codex-native Agentic OS, with Claude Code retained as the Development execution lane.

    line 4
  2. Distinctive:

    Update docs whenever workflow or architecture changes.

    line 12
  3. Distinctive:

    If any check is skipped, report it explicitly.

    line 24
  4. Distinctive:

    Keep destructive capabilities behind explicit configuration gates.

    line 27
  5. Distinctive:

    Never broaden destructive behavior without explicit user request.

    line 28
  6. Distinctive:

    Treat hook execution path as fail-safe and non-blocking.

    line 29

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

Project intent

  • Keep this repository a stable, local-first Codex-native Agentic OS, with Claude Code retained as the Development execution lane.
  • Present provider-neutral missions, permissions, scheduling, and observability; providers supply bounded capabilities rather than separate product consoles.
  • Maintain correctness across hooks, API, DB, websocket, UI, and MCP integration.

Priorities

  • Correctness over cleverness.
  • Small, scoped, reversible diffs.
  • Preserve existing behavior unless change is requested.
  • Update docs whenever workflow or architecture changes.

Where to work

  • server/ for API/routes/data processing.
  • client/ for React UI behavior.
  • mcp/ for local MCP server tooling.
  • scripts/ for hook/install/import/cleanup utilities.

Validation expectations

  • Backend changes: run npm run test:server when possible.
  • Frontend changes: run npm run test:client when possible.
  • MCP changes: run npm run mcp:typecheck and npm run mcp:build.
  • If any check is skipped, report it explicitly.

Safety expectations

  • Keep destructive capabilities behind explicit configuration gates.
  • Never broaden destructive behavior without explicit user request.
  • Treat hook execution path as fail-safe and non-blocking.

Useful commands

  • Setup: npm run setup
  • Dev: npm run dev
  • Build/start: npm run build then npm start
  • MCP helpers: npm run mcp:install, npm run mcp:build, npm run mcp:start

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