Initialize Project Instructions with Hermes /init

/init [notes] scans a repository and creates or updates AGENTS.md, the project instruction file Hermes can load automatically. It inspects manifests, layout, and toolchain configuration with read-only tools before writing concise operating guidance.

Official context-file guide: https://hermes-agent.nousresearch.com/docs/user-guide/features/context-files

Use repository evidence

Run /init from the actual project root. Optional notes can emphasize a test command, deployment boundary, coding convention, or sensitive subsystem, but they should not replace the scan. If AGENTS.md already exists, the command is designed to merge-update it while preserving useful human-authored content.

Keep the file focused on durable project facts: how to build and test, important directories, required checks, formatting conventions, and actions that need approval. Do not place secrets, temporary task state, or lengthy architecture histories in automatic context.

Initialization checklist

Confirm the current working directory is the intended repository root.
Review manifests and existing contributor instructions.
Supply notes only for real, durable priorities.
Preserve stricter existing safety and release rules.
Record exact build, test, lint, and deploy commands.
Explain public/private or generated/source boundaries.
Keep credentials and environment values out of the file.
Review the diff before accepting the update.

Write for future agents

Instructions should be unambiguous and executable. Prefer “Run npm test before deployment” over “test carefully.” Name paths relative to the project root. Separate mandatory release gates from optional development tips, and state what must not be modified when concurrent work or generated artifacts are present.

Pitfalls

Running /init from a parent directory that contains several projects.
Replacing carefully maintained instructions with generic boilerplate.
Recording a one-time workaround as a permanent rule.
Embedding tokens, hostnames, or personal filesystem details.
Listing commands that were never executed successfully.
Making the file so long that essential boundaries disappear.

Verification steps

Inspect the AGENTS.md diff line by line.
Run every mandatory command that the file claims is current.
Verify named directories and configuration files exist.
Check that existing safety rules were preserved.
Start a fresh Hermes session in the project and confirm the context is loaded.
Ask for a simple repository task and verify the agent follows the documented workflow.