Kilo-OrgAGENTS.mdkilocode
Kilo-Org/kilocode/AGENTS.md
reach for `let`. ### Naming Enforcement (Read This) THIS RULE IS MANDATORY FOR AGENT WRITTEN CODE. - Use single word names by default for new locals, params, and helper functions. - Multi-word
AGENTS.md examples from real projects
How real projects brief Codex, Cursor and every other agent that reads AGENTS.md.
Best matches · from page 7Worked for most · soon
Kilo-OrgAGENTS.md
deepset-aiAGENTS.mdhaystack
deepset-ai/haystack/AGENTS.md
CONTRIBUTING.md](CONTRIBUTING.md#release-notes) for details. In addition, there are rules inferred from previous code reviews. Follow them like a reviewer's note: they encode reasons, not ceremony, so when
MicrosoftAGENTS.mdwinget-cli
microsoft/winget-cli/AGENTS.md
open a pull request or link a branch when code is available. ## Pull requests Before opening a pull request: 1. Review `CONTRIBUTING.md` and follow the repository PR template. 2. Keep
EveryIncAGENTS.mdcompound-engineering-plugin
EveryInc/compound-engineering-plugin/AGENTS.md
path the old text served. - Ordinary code under `src/`, `tests/`, and `scripts/` gets ordinary code review; these rules are about instruction prose. ### Acting on review feedback This governs any agent
activepiecesAGENTS.mdactivepieces
activepieces/activepieces/AGENTS.md
surface needs the placeholder. ## Key Utilities (`@activepieces/shared`) `apId()`, `tryCatch()`, `tryCatchSync()`, `isNil()`, `spreadIfDefined()`, `spreadIfNotUndefined()`, `ActivepiecesError({ code, params })`, `SeekPage `, `formErrors`, `BaseModelSchema`, `chunk()`, `partition()`, `unique()`, `omit()`, `sanitizeObjectForPostgresql()` ## Testing ```bash npm run test-unit
Model Context ProtocolAGENTS.mdpython-sdk
modelcontextprotocol/python-sdk/AGENTS.md
narrate the code or restate names, types, or assertions. - Type hints required for all code - Public APIs must have docstrings. When a public API raises exceptions a caller would reasonably
pascalorgAGENTS.mdeditor
pascalorg/editor/AGENTS.md
wiki/architecture/tools.md`. ## When making architecture-sensitive changes Read the relevant page in `wiki/architecture/` **before** writing code. The page list lives in `wiki/architecture/README.md`. As a minimum: - Adding a node type → `node-schemas.md`, `renderers.md
SuperClaude-OrgAGENTS.mdSuperClaude_Framework
SuperClaude-Org/SuperClaude_Framework/AGENTS.md
install` once, then `npm test` or `npm run build`; repeat for `research/` and `index/`. ## Coding Style & Naming Conventions - Python: 4-space indentation, Black line length 88, Ruff
coleam00AGENTS.mdArchon
coleam00/Archon/AGENTS.md
archon/workflow-language-constitution.md`](.archon/workflow-language-constitution.md), aspirational engineering craft and review values in [`.archon/engineering.md`](.archon/engineering.md), user documentation in the docs site, and machine-checkable rules in code, types, tests, lint, or CI. ## Read before
czlonkowskiAGENTS.mdn8n-mcp
czlonkowski/n8n-mcp/AGENTS.md
every code change and `npm run build` after MCP server changes. - After rebuilding server code, ask the user to reload the MCP server before testing the changed MCP behavior. - Name
NVIDIAAGENTS.mdNemoClaw
NVIDIA/NemoClaw/AGENTS.md
rerun affected checks without asking at each step. Continue into PR publication and review follow-up when requested. A first patch or lifecycle handoff is not completion. Keep local verification
NVIDIAAGENTS.mdNemoClaw
NVIDIA/NemoClaw/docs/AGENTS.md
review documentation. This file owns agent-specific documentation routing and workflow. - Write clear, accurate, task-oriented documentation for developers who run NemoClaw with OpenClaw, Hermes, LangChain Deep Agents Code
NVIDIAAGENTS.mdNemoClaw / tools
NVIDIA/NemoClaw/.dsh/tools/AGENTS.md
they matter. - Prefer a direct, focused tool over overlapping projections or orchestration layers. Ordinary code review, representative harness exercises, and repository hooks are the validation boundary. Do not add repository
NVIDIAAGENTS.mdNemoClaw / messaging
NVIDIA/NemoClaw/src/lib/messaging/AGENTS.md
messaging egress opt-in unless accepted product policy states otherwise. Load `nemoclaw-maintainer-security-code-review` when the change affects credentials, public ingress, sender authorization, network policy, or another trust
steipeteAGENTS.mdCodexBar
steipete/CodexBar/AGENTS.md
handoff; add focused `swift test --filter ...` runs for parser/provider fixes when possible. - After any code change, run `make check` and fix all reported format/lint issues before handoff. - Prefer CLI/focused tests
MicrosoftAGENTS.mdonnxruntime
microsoft/onnxruntime/AGENTS.md
github/skills/). Load each skill whose description matches the requested task, subsystem, or behavior. For code reviews, follow the `/code-review` skill in addition to relevant domain skills and matching path-scoped
Hugging FaceAGENTS.mdpeft
huggingface/peft/.ai/AGENTS.md
Pure code-agent PRs are not allowed: a human submitter must understand and be able to defend the change end-to-end. - The submitting human is responsible for reviewing every
GitHubAGENTS.mddocs / responsible-use
github/docs/content/copilot/responsible-use/agents.md
GitHub Copilot includes several agentic features that go beyond suggestion and conversation—they can review code, take action on your behalf, and build applications. This card covers the following experiences
JetBrainsAGENTS.mdintellij-community
JetBrains/intellij-community/AGENTS.md
order. - User-visible strings belong in `*.properties` for localization. ## Language - Read [Code Style](./.agents/skills/code-style/SKILL.md) before writing or reviewing Kotlin or Java. ## Writing Write every user-visible artifact in [ASD-STE100
GoogleAGENTS.mdfilament
google/filament/AGENTS.md
Synchronization guidelines for Java/JNI (Android) and JavaScript/TypeScript (Web/WASM) when public C++ APIs change. ### 6. Code Review & Invariant Auditing * [skills/code_review/SKILL.md](skills/code_review/SKILL.md): Adversarial systems, concurrency, memory-model, and architecture code review protocol
About AGENTS.md
What is AGENTS.md?
An open format for instructions to coding agents, read by Codex, Cursor and others. Think of it as a README written for agents.
Where does it go?
At the repository root, with more specific files in subdirectories. Agents read the one closest to the file they're editing.
What should it contain?
Setup and test commands, code style, and the rules a new contributor would need to know.
Does Claude Code read it?
Claude Code reads CLAUDE.md. A one-line CLAUDE.md that points at AGENTS.md covers both.