agentleFS
imbue-aiimbue-ai/sculptor/openhost-agent/AGENTS.md

sculptor / openhost-agent

AGENTS.md246 starsChanged 5 months agoMITView on GitHub

This file was seeded on the first deployment of this Sculptor app, and it persists across reloads/rebuilds — it lives in the backed-up app-data dir ($OPENHOST_APP_DATA_DIR). You are running inside an OpenHost-hosted Sculptor; detect that from the OPENHOST_* env vars (e.g. OPENHOST_APP_NAME). This file is yours. Put any standing, system-wide instructions for agents here freely — nothing in the deploy will overwrite it. For the current, maintained specifics of this environment — storage and what survives restarts, where/how to add…

The file

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

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    This file is yours: Put any standing, system-wide instructions for agents here freely — nothing in the deploy will overwrite it.

    line 8

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

OpenHost Sculptor — standing agent notes (seeded on first deploy)

This file was seeded on the first deployment of this Sculptor app, and it persists across reloads/rebuilds — it lives in the backed-up app-data dir ($OPENHOST_APP_DATA_DIR). You are running inside an OpenHost-hosted Sculptor; detect that from the OPENHOST_* env vars (e.g. OPENHOST_APP_NAME).

This file is yours. Put any standing, system-wide instructions for agents here freely — nothing in the deploy will overwrite it.

For the current, maintained specifics of this environment — storage and what survives restarts, where/how to add repositories and authorize gh, and what the /proxy/<port>/ capability can and can't do — use the openhost-environment skill. That skill ships with the deploy image and is refreshed on every release, so it stays up to date as the environment evolves.

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.