agentleFS
Sign inStart free
jxpeng98jxpeng98/qiongli/AGENTS.md

qiongli

AGENTS.md26 starsChanged 3 months agoMITView on GitHub

- Deliver the CLI-first research workflow through native CLI, Plugin/Skills and MCP. Codex is the primary development and verification Host; other Agents adapt the shared contracts. Preserve compatibility and the user's configured models. The retained Desktop is maintenance scope, not the current delivery target. - The master roadmap owns direction and the execution horizon; read its current bounded plan. The program ledger owns task status and accepted evidence. Keep changing progress there and in the plan, not duplicated here. Local…

  • 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,439 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 repository3 other files it gives its agents.

The file

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

3 rules. About 0 are common, 1 is distinctive, and 2 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.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read relevant .trellis/spec/ contracts when changing their package/layer.

    line 15
  2. Very specific:

    Follow CONTRIBUTING.md: local feature branch → affected checks → review and scoped commits → local fast-forward merge into 2.x.

    line 21
  3. Distinctive:

    Run the closest meaningful checks, retaining validation, permission, compatibility and data-loss negative cases.

    line 28

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

Project instructions

Direction and sources

  • Deliver the CLI-first research workflow through native CLI, Plugin/Skills and MCP. Codex is the primary development and verification Host; other Agents adapt the shared contracts. Preserve compatibility and the user's configured models. The retained Desktop is maintenance scope, not the current delivery target.
  • The master roadmap owns direction and the execution horizon; read its current bounded plan. The program ledger owns task status and accepted evidence. Keep changing progress there and in the plan, not duplicated here. Local checks or merges do not establish acceptance.
  • Accepted ADRs own architecture; supersede them rather than rewriting history. Read relevant .trellis/spec/ contracts when changing their package/layer. Retained .trellis/ records are project knowledge, not a mandatory task engine; do not reinstall Trellis skills, hooks or agents unless requested.

Development and integration

  • Follow CONTRIBUTING.md: local feature branch → affected checks → review and scoped commits → local fast-forward merge into 2.x. These local actions are authorized for requested work without per-step approval; no PR or remote CI wait is required.
  • Inspect the diff and trace behavior to its existing owner. State the smallest useful outcome and reuse the current plan; routine fixes need no new task/PRD, context manifest or journal. Edit canonical sources, not generated copies.
  • Run the closest meaningful checks, retaining validation, permission, compatibility and data-loss negative cases. Reuse results until code, dependencies or inputs change; commit/merge alone does not warrant a rerun.
  • Review the final diff, update affected contracts, and record checks, remaining gaps and the next increment once at integration. External evidence gates readiness claims, not independent development.
  • The main Agent may implement and check directly. Delegate only useful, bounded independent work with clear file ownership and a shared interface.
  • Preserve unrelated changes and user data. Qiongli project writes use the existing preview/approval/CAS owners. Material scope changes, private research access, destructive actions, push, remote-rule changes and publication require authority for that action; local coding authorization does not imply it.

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