temper-pass
AGENTS.md0 starsChanged 47 days agoMITView on GitHub
This repo uses ForgeTrail lifecycle tracking. Source of truth: .forgetrail/workflow_tracking.json (currentPhase, phases, decisions). Do not advance currentPhase or mark a phase complete without explicit user confirmation. If exit criteria look satisfied, say so and wait.
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,542 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 repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .forgetrail/CLAUDE.mdCLAUDE.md
- .cursor/rules/commit-messages.mdcCursor rule
- .cursor/rules/forgetrail-lessons-gate.mdcCursor rule
- .cursor/rules/forgetrail-lessons-mcp.mdcCursor rule
- .cursor/rules/forgetrail-phase-status.mdcCursor rule
- .cursor/rules/git-user-commits.mdcCursor rule
The file
We split this AGENTS.md into the rules it gives an agent
4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 7
Read .forgetrail/workflow_tracking.json and CONTEXT_PROMPT.md (once it exists) before making changes.
- Very specific: line 8
Check currentPhase and work within that phase's scope.
- Very specific: line 13
Commit after substantive work per .cursor/rules/git-user-commits.mdc.
- Very specific: line 17
Do not advance currentPhase or mark a phase complete without explicit user confirmation.
≈ “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
Agent guardrails — TemperPass
This repo uses ForgeTrail lifecycle tracking. Source of truth: .forgetrail/workflow_tracking.json (currentPhase, phases, decisions).
Session start
- Read
.forgetrail/workflow_tracking.jsonandCONTEXT_PROMPT.md(once it exists) before making changes. - Check
currentPhaseand work within that phase's scope; don't jump ahead without user confirmation.
Git commits
- Plain
git commit -m "..."orgit commit -F <file>. - Commit after substantive work per
.cursor/rules/git-user-commits.mdc. Do not push unless the user explicitly asks.
Phase transitions
Do not advance currentPhase or mark a phase complete without explicit user confirmation. If exit criteria look satisfied, say so and wait.
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.