wrap-session
AGENTS.md0 starsChanged 2 months agoMITView on GitHub
Type: coding · Ownership: tool · Delivery mode: local-only Harness-neutral skill: clean session exit. Owner gate on persist and Git actions, then receipt at ~/.local/state/session-wrap/. Receipt present means clean close; missing after real work means likely missed wrap. Optional Hermes detector: bin/wrap-status.sh. Read-only over receipts and Hermes state DB. Explicit bin/wrap-status.sh init creates receipt directory and .enabled-at baseline. Subagent and tool sessions are excluded. Tests: bash tests/run-tests.sh (plain Bash, no framework). Keep this file for knowledge useful to almost every…
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,843 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 repository2 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- wrap-sessionSkill
The file
We split this AGENTS.md into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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
- Distinctive: line 17
Keep this file for knowledge useful to almost every future agent session in this project.
- Distinctive: line 18
Do not repeat what the codebase already shows.
- Distinctive: line 19
Prefer rewriting or pruning existing entries over appending new ones.
- Distinctive: line 20
When updating this file, preserve this bar for all agents and keep entries concise.
≈ “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
wrap-session
Type: coding · Ownership: tool · Delivery mode: local-only
Harness-neutral skill: clean session exit. Owner gate on persist and Git actions,
then receipt at ~/.local/state/session-wrap/. Receipt present means clean
close; missing after real work means likely missed wrap.
Optional Hermes detector: bin/wrap-status.sh. Read-only over receipts and
Hermes state DB. Explicit bin/wrap-status.sh init creates receipt directory
and .enabled-at baseline. Subagent and tool sessions are excluded.
Tests: bash tests/run-tests.sh (plain Bash, no framework).
Maintaining this file
Keep this file for knowledge useful to almost every future agent session in this project. Do not repeat what the codebase already shows; point to the authoritative file or command instead. Prefer rewriting or pruning existing entries over appending new ones. When updating this file, preserve this bar for all agents and keep entries concise.
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.