ghost-alice
AGENTS.md15 starsChanged 32 days agoApache-2.0View on GitHub
The common rules for this work come from the current host's installed common contract. Read it through the host's loader and use the current session metadata (the [session-intent-receipt] block) exactly as supplied; the contract's source in this repository does not replace the installed common contract as the authority for execution. Codex loads its contract from ~/.codex/ghost-alice-governance.md; Claude Code receives its contract in ~/.claude/CLAUDE.md. For development, platforms/common-governance.md is the source of the common contract. The installer combines that source and a…
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,774 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 repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- adversarial-verificationSkill
- agent-security-scanSkill
- boundary-contractSkill
- compact-handoffSkill
- merge-companionSkill
- necessity-gateSkill
- session-intent-analyzerSkill
- skill-evolutionSkill
- task-routerSkill
The file
We split this AGENTS.md into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Before editing a skill, follow official-docs/derived/skill-compliance-checklist.md, phases 1–5.
- Distinctive: line 14
Write each Markdown prose paragraph on one physical source line unless Markdown, syntax or protocol fields require separate lines.
≈ “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.
Files
Ghost-ALICE Project Instructions
The common rules for this work come from the current host's installed common contract. Read it through the host's loader and use the current session metadata (the [session-intent-receipt] block) exactly as supplied; the contract's source in this repository does not replace the installed common contract as the authority for execution. Codex loads its contract from ~/.codex/ghost-alice-governance.md; Claude Code receives its contract in ~/.claude/CLAUDE.md.
For development, platforms/common-governance.md is the source of the common contract. The installer combines that source and a template under platforms/<host>/ into the installed common contract. Read these source files only when the authorized development task needs them.
Project work follows the source file that the user selected as the owner. Preserve existing changes, and keep these results distinct: a source modification, a verification, an installation and the host's actual adoption of the change.
Development rules
- Keep
platforms/common-governance.mdhost-neutral. Templates underplatforms/<host>/carry only host mechanics such as skill loading, installed paths and hook stages; they do not restate common rules. The exception is a rule that the response model needs before it has read the contract or when it cannot read it: the Codex bootstrap states the contract's direct-answer condition and its no-substitution prohibition in the contract's words, because the response model under Codex reads the contract only through a tool call. - Name the actor, action, input, output, recipient and condition. Each owning procedure describes its handoff once; other documents refer to it. Write current behavior without historical alternatives. Keep paired English and Korean documents and their diagrams consistent with each other and with the documents and code that call them.
- Before editing a skill, follow
official-docs/derived/skill-compliance-checklist.md, phases 1–5. KeepSKILL.mdshort, detailed procedures inreferences/, and executables inscripts/. - Write each Markdown prose paragraph on one physical source line unless Markdown, syntax or protocol fields require separate lines.
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.