Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add rules/autonomous-ai/autonomous-os/docs-on-code-changegit clone --depth 1 https://github.com/autonomous-ai/autonomous-osWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00339 | $0.00339 |
| Opus 5 | $0.00169 | $0.00169 |
| Sonnet 5 | $0.00068 | $0.00068 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
docs-on-code-change scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Docs on Code Change
Whenever you write or change code that affects behavior, architecture, or APIs, you must update the relevant documentation in docs/.
Scope
- New features, refactors, API changes, config changes, startup flow changes
- Applies to:
internal/,server/,domain/,scripts/,web/,bootstrap/
Actions
- Identify which
docs/*_vi.mdfiles are impacted - Update them to match the new code (numbers, flows, endpoints, states, etc.)
- Keep docs accurate — no drift between code and documentation
Doc Files
| Code area | Docs to update |
|---|---|
| lamp-server, API, startup | lamp-server_vi.md |
| LED, effects, states, animations | led-control_vi.md |
| Setup flow, provisioning | setup-flow_vi.md |
| Web UI, configuration pages | web-ui_vi.md |
| Flow Monitor (pipeline SVG, flow logs) | flow-monitor_vi.md (and docs/flow-monitor.md) |
| Overall structure | overview_vi.md |
| MQTT, dispatch, publish | mqtt_vi.md |
| bootstrap, OTA | bootstrap-server_vi.md |
Convention
- Vietnamese docs:
*_vi.md(e.g.lamp-server_vi.md) - English vision/design: keep as-is unless code explicitly changes behavior
- 100% accurate: numbers, names, flows must match code
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 39 lines · 339 tokens per session scan A 6953a9268aef
docs-on-code-change is a cursor rule published in the GitHub repository autonomous-ai/autonomous-os (256 stars, last pushed 3d ago), licensed Apache-2.0. It adds 339 tokens to every session, about $0.0017 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other cursor rules, from other repositories
frontend
Frontend design-system rules for packages/web (tokens, components, i18n).
cursorrules
Robot control server. Do not move the physical robot without checking health first.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.