live-agentic-html-editor
AGENTS.md5 starsChanged 28 days agoMITView on GitHub
This file is about the tool: how your agent host connects to it, how to install it, and where the documentation is. The instructions for running a review are in the lahe skill, skills/lahe/SKILL.md. Once the skill is installed, your host loads it when a review comes up. If your host does not load skills, read that file before you start a review. Every host uses the same command, lahe, and the same skill text. Two things differ by host:…
- Installs packages
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 repository4 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- laheSkill
- maintain-verification-skillSkill
- verify-laheSkill
The file
We split this AGENTS.md into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Every host uses the same command, lahe, and the same skill text.
- Very specific: line 31
Stop hook, lahe hook stop, to ~/.claude/settings.json (see docs/CLI.md, "The Stop hook").
≈ “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
For agents: the live agentic HTML editor
This file is about the tool: how your agent host connects to it, how to install
it, and where the documentation is. The instructions for running a review are in
the lahe skill, skills/lahe/SKILL.md. Once the skill is installed, your host
loads it when a review comes up. If your host does not load skills, read that
file before you start a review.
How each host connects
Every host uses the same command, lahe, and the same skill text. Two things
differ by host: where it finds the skill, and how it waits for the reviewer's
next comment without spending model turns.
| Host | Finds the skill at | Waits for work with |
| Claude Code | ~/.claude/skills/lahe/SKILL.md | lahe monitor --session <id>, run with Bash in the background and launched again after each batch |
| Codex | ~/.agents/skills/lahe/SKILL.md | lahe monitor --session <id> --codex, returns after starting a watcher that queues real work to the same conversation |
| Gemini CLI | ~/.agents/skills/lahe/SKILL.md | lahe monitor --session <id>, run in the foreground |
| Antigravity | read skills/lahe/SKILL.md from the clone | lahe monitor --session <id>, run as a background terminal task |
| Any other host | read skills/lahe/SKILL.md from the clone | lahe monitor --session <id>, run in the foreground |
npm run install-skills copies the skill to both skill folders, with its
references/ beside it (the task runbooks, host monitor guides, and component
catalog from vendor/stclair-doc-style/COMPONENTS.md), and adds Claude Code's
Stop hook, lahe hook stop, to ~/.claude/settings.json (see
docs/CLI.md, "The Stop hook"). lahe review
prints the exact monitor command for each session.
Writing new text
A reviewer can write new paragraphs, headings, and lists on a page, and can start a blank notes page with lahe write notes/day.md. That command prints what lahe review prints, so the wake and drain steps are the same. The items that come back carry new_blocks, and the rules for placing them are in the skill's references/free-writing.md. How it works inside is docs/ongoing/FREE_WRITING.md.
Install
See docs/INSTALL.md. pandoc 3 is optional: with it, Markdown fenced divs
(::: callout-req) render as styled panels. When the rail says "Ask your agent
to install pandoc to get the correct styles", install it (brew install pandoc
on macOS); the running helper finds it within a minute, and the next page load
draws the panels.
Documentation
skills/lahe/SKILL.mddocs/INSTALL.mddocs/CLI.mddocs/CONTRACTS.mddocs/ongoing/FREE_WRITING.mddocs/diagrams/
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.

