AGENTS.md@examples/schedulingA
AGENTS.md@examples/scheduling from gbourgeat/ddd-ts-kit is an AGENTS.md file: the standing instructions coding agents read in that repo.
mdr add gbourgeat/ddd-ts-kit/examples/scheduling/AGENTS.md@git:20261018.082015dPins git:20261018.082015d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- AGENTS.md file
- Repository
- gbourgeat/ddd-ts-kit
- Path
examples/scheduling/AGENTS.md- Versions recorded
- 5
- Latest version
- git:20261018.082015d, committed Oct 18, 2026
- First version recorded
- Oct 13, 2026
- Size
- 6,406 bytes
- Repository stars
- 7
- License
- MIT
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# scheduling A ddd-ts-kit project: one bounded context per directory of `src/contexts/`, each described by its `CONTEXT.md`. The plan and what is next: `docs/architecture/plan.md`, when the project follows the method. ## Commands - `npm run verify`: types, lint, format, tests with the coverage thresholds of `ddd-ts-kit.config.json` (per context and layer), architecture rules, import graph, dead code, documentation drift. Once, before a commit that closes a slice. A layer under its threshold gets the missing test, never an exclusion. - `npx ddd-ts-kit check --changed-since <ref>`: the architecture rules on what changed; `npx ddd-ts-kit explain <rule-id>` gives the reason and an example. - `npx ddd-ts-kit list --json`: the map of the contexts. `npx ddd-ts-kit describe <context> --json`: one context as data (use cases, routes, events, ports, dependencies). - `npx ddd-ts-kit status`: the next step of the plan, the slices by status, the markers left per context. `npx ddd-ts-kit todo [<context>]`: each remaining `TODO(domain)` and `it.todo` as `file:line`. …
Read the whole file at its exact version.
How to install
mdr add gbourgeat/ddd-ts-kit/examples/scheduling/AGENTS.md@sha256:c1ef2d2051b0830dThe line at the top of this page pins the label git:20261018.082015d, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_kbphkycfiixbhn75)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 13, 2026 and Oct 18, 2026, about one every day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261018.082015d latest | 2026-10-18 | 082015d | 6,406 B | A | view · diff |
| git:20261018.5d99527 | 2026-10-18 | 5d99527 | 6,418 B | A | view · diff |
| git:20261017.9fa9fd4 | 2026-10-17 | 9fa9fd4 | 6,333 B | A | view · diff |
| git:20261017.5af6d8b | 2026-10-17 | 5af6d8b | 6,211 B | A | view · diff |
| git:20261013.35e7888 | 2026-10-13 | 35e7888 | 6,203 B | A | view |
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (6406 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
gbourgeat/ddd-ts-kit · 7 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kbphkycfiixbhn75 GET https://markdownregistry.com/api/v1/resolve?ref=gbourgeat/ddd-ts-kit/examples/scheduling/AGENTS.md GET https://markdownregistry.com/api/v1/blob/c1ef2d2051b0830df3db5c7a09f34682855c2da75d01f63bfb4af88d7140ca4c
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: how to write a good AGENTS.md · AGENTS.md vs CLAUDE.md · which agent file does what.