Agmente / AgmenteTests
AGENTS.md545 starsChanged 9 months agoMITView on GitHub
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 32,671 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 repository13 other files it gives its agents.
- ACPClient/AGENTS.mdAGENTS.md
- Agents.mdAGENTS.md
- Agmente/AGENTS.mdAGENTS.md
- AgmenteUITests/AGENTS.mdAGENTS.md
- AppServerClient/AGENTS.mdAGENTS.md
- e2e/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- acp-local-runnerSkill
- codex-local-cli-e2eSkill
- repeat-with-delaySkill
- upstream-protocol-drift-watchSkill
- run-agmente-codex-e2eSkill
- run-agmente-e2eSkill
The file
We split this AGENTS.md into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
- Very specific: line 7
If a test change requires checking ACP/Codex upstream behavior, read .agmente.paths from repo root.
- Very specific: line 8
Use AGMENTE_ACP_REPO and AGMENTE_CODEX_REPO for local external checkout paths.
- Distinctive: line 17
Prefer in-memory storage and deterministic setup.
- Distinctive: line 18
Avoid live network dependencies in unit tests.
- Distinctive: line 21
Keep test names behavior-oriented so refactors do not require doc edits.
≈ “Common” is an estimate: at least 1 in 5 of the 41,581 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.
Files
Agmente Unit Tests Guide
Scope
Unit/integration-style tests for app-layer view models and persistence.
External Repo Paths
- If a test change requires checking ACP/Codex upstream behavior, read
.agmente.pathsfrom repo root. - Use
AGMENTE_ACP_REPOandAGMENTE_CODEX_REPOfor local external checkout paths.
Test Layers
- Protocol routing and view-model synchronization tests.
- ACP-specific session behavior tests.
- Codex-specific thread/session behavior tests.
- Storage and persistence behavior tests.
Test Design Rules
- Prefer in-memory storage and deterministic setup.
- Avoid live network dependencies in unit tests.
- Validate protocol-switch behavior explicitly (ACP -> Codex and ACP-only paths).
- Cover metadata behaviors that impact UI ordering and session/thread summaries.
- Keep test names behavior-oriented so refactors do not require doc edits.
When Updating Tests Is Required
- Any change to session/thread lifecycle logic.
- Any change to protocol detection/switching.
- Any change to summary parsing (
cwd, timestamps, previews).
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
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.

