deepseek-harness / schedule
deepseek-ai/deepseek-harness/packages/schedule/AGENTS.md
delivery. - Keep recurrence arithmetic pure. Production uses platform wall time and segmented timers; tests use explicit samples or restored fake timers
How real projects brief Codex, Cursor and every other agent that reads AGENTS.md.
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.
deepseek-ai/deepseek-harness/packages/schedule/AGENTS.md
delivery. - Keep recurrence arithmetic pure. Production uses platform wall time and segmented timers; tests use explicit samples or restored fake timers
deepseek-ai/deepseek-harness/scripts/AGENTS.md
ownership gates use syntax-aware discovery, guard against an empty or narrowed corpus, and test every admitted/excluded form that changes their detection boundary. Script specs run in forked workers beside
Steady8 mentions in 2 weeks
4 projects use a version of this
deepseek-ai/deepseek-harness/snapshots/AGENTS.md
AGENTS.md — Recorded-session snapshots This tree contains only tests whose committed session JSONL is replay input and expected persisted output. Keep non-session ARIA, geometry, generator, CLI, and unit expected
Steady8 mentions in 2 weeks
1 project uses a version of this
deepseek-ai/deepseek-harness/snapshots/session/agent-instructions-budget-chains/workspace/.dsh/AGENTS.md
project. Reply in short, plain sentences and state the result first. Run the narrowest test that covers a change before reporting it as done. Never commit, push, or delete branches
deepseek-ai/deepseek-harness/website/AGENTS.md
block because tab switching is unavailable; the [code-group adapter](.vitepress/code-groups.ts) and its [focused tests](tests/code-groups.spec.ts) own this behavior. Long tables with at least ten data rows receive independent text
NousResearch/hermes-agent/agent/AGENTS.md
CHILD_ENV_MARKER` valued as the fenced Kanban board root, not a bare flag. ## Tests Loop/phase tests go in `tests/agent/`; patch the binding the phase actually reads (siblings often `from
No other project uses it yet
NousResearch/hermes-agent/AGENTS.md
refactors; extending before duplicating (3+ PRs in one category → an ABC + orchestrator); behaviour-contract tests; E2E with real imports against a temp `HERMES_HOME` for resolution, config, security
Steady3 mentions in 2 weeks
No other project uses it yet
NousResearch/hermes-agent/cron/AGENTS.md
root, so a child working against a scratch `HERMES_HOME` keeps a writable board. ## Tests `tests/cron/`, `tests/hermes_cli/test_kanban*.py`, `tests/tools/test_kanban*.py`. Schedule parsing and catch-up windows are pure functions — test
NousResearch/hermes-agent/gateway/AGENTS.md
exists. A sealed native stream is a regular message — `chat.update` works (live-verified). Contract tests: `tests/gateway/test_stream_final_contract.py` (mutation-checked). Slack ground truth: `chat.*Stream` speaks STANDARD markdown, not mrkdwn; `stopStream.markdown_text
NousResearch/hermes-agent/hermes_cli/AGENTS.md
ROOT_KEYS`). For a new key: `rg -n '" "' hermes_cli/config_defaults.py` AND `rg -n ' ' --glob '!tests' .` both hit, and one invariant test sets it in a temp `config.yaml` and asserts
NousResearch/hermes-agent/plugins/AGENTS.md
process warning, documented replacement + migration note, ≥ 2 subsequent minor releases before removal. - Compat tests load **frozen plugins through the real discovery path** and assert outcomes — never exact registry/catalog counts, source
NousResearch/hermes-agent/pm/AGENTS.md
plugin may move a transitive core package within core's declared ranges (`tests/pm/test_workspace_build_inputs.py::test_plugin_can_move_compatible_transitive_but_not_exact_requirement`). Plugin `python_dependencies` follow the plugin
Steady3 mentions in 2 weeks
No other project uses it yet
NousResearch/hermes-agent/skills/AGENTS.md
every call — ship a helper script and reference it by skill-relative path. 7. **Tests at `tests/skills/test_ _skill.py`**, stdlib + pytest + `unittest.mock` only, no live network. Run `scripts/run_tests.sh tests/skills/test_ _skill.py
Steady3 mentions in 2 weeks
No other project uses it yet
NousResearch/hermes-agent/tests/AGENTS.md
tests/ — how Hermes tests are written and run Applies on top of the root `AGENTS.md`. Read it before adding or changing any test. ## Running tests **ALWAYS use `scripts/run_tests.sh`**, never bare
No other project uses it yet
NousResearch/hermes-agent/tools/AGENTS.md
skills, terminal, todo, tts, video, vision, web, yuanbao` (don't assert the list in tests). Per-platform enable/disable via `hermes tools` (curses) or `tools. .enabled/disabled` in config.yaml. `browser_exec
NousResearch/hermes-agent/tui_gateway/AGENTS.md
import; the dispatcher rejects unknown param keys (`4000` + key path) and, under `HERMES_TEST_ISOLATION=1`, raises `ContractViolation` when a handler's result or an emitted payload does not match
NousResearch/hermes-agent/web/AGENTS.md
surface; a new surface is a new `web_routers/ .py`, not a growing `web_server.py`. - Tests: Python in `tests/hermes_cli/` (routers, pty bridge); JS in the `web/` vitest suite. Python tests must
affaan-m/ECC/AGENTS.md
Core Principles 1. **Agent-First** — Delegate to specialized agents for domain tasks 2. **Test-Driven** — Write tests before implementation, 80%+ coverage required 3. **Security-First** — Never compromise on security; validate
Steady32 mentions in 2 weeks
No other project uses it yet
affaan-m/ECC/.codex/AGENTS.md
guidance, read `docs/CODEX-NAVIGATION-GUIDE.md` after this supplement. ## Model Recommendations | Task Type | Recommended Model | |-----------|------------------| | Routine coding, tests, formatting | GPT 5.5 | | Complex features, architecture | GPT 5.5 | | Debugging, refactoring | GPT 5.5 | | Security review
Steady32 mentions in 2 weeks
1 project uses a version of this
TheAlgorithms/Python/AGENTS.md
change code and its doctests in the same PR.** If you're only updating tests, say so and touch nothing else. ## Code conventions (enforced by CI) - **Formatting & linting:** `ruff
No other project uses it yet
An open format for instructions to coding agents, read by Codex, Cursor and others. Think of it as a README written for agents.
At the repository root, with more specific files in subdirectories. Agents read the one closest to the file they're editing.
Setup and test commands, code style, and the rules a new contributor would need to know.
Claude Code reads CLAUDE.md. A one-line CLAUDE.md that points at AGENTS.md covers both.