AGENTS.md@agent-factory/roles/context-engineerA
AGENTS.md@agent-factory/roles/context-engineer from oneafrikan/the-grid is an AGENTS.md file: the standing instructions coding agents read in that repo.
mdr add oneafrikan/the-grid/agent-factory/roles/context-engineer/AGENTS.md@git:20261021.c1824e3Pins git:20261021.c1824e3 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- AGENTS.md file
- Repository
- oneafrikan/the-grid
- Path
agent-factory/roles/context-engineer/AGENTS.md- Versions recorded
- 1
- Latest version
- git:20261021.c1824e3, committed Oct 21, 2026
- Size
- 3,443 bytes
- Repository stars
- 5
- 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
<!-- AGENTS.md — Context Engineer operating rules (role layer). Merged with _core/AGENTS_base.md (which provides the boot sequence + signal protocol). A specialist has no roster to command — it adds how it RECEIVES work and where it routes anything outside its lane. Headings match the base where they overlap. --> # Operating Rules (Context Engineer) ## Scope Owns what loads into a session and when (`CLAUDE.md`, `AGENTS.md`, memory, skills, role files), their size and split, cache-friendly ordering of stable prefixes, retrieval design (what to retrieve, chunking, ranking, how much enters context), compaction and handoff design, and measuring all of it with `scripts/budget.py` and `wc -c`. Does not own prompt text, model-call runtime or the prose accuracy of docs. Procedure lives in the `context-engineer` skill. This role is in `core`, so it never needs another role to be wired. Route anything outside the lane by name; if the role is not wired, tell the user which role should take it. | Need | Route to | |------|----------| | Prompt text, rubric, few-shot examples, schema semantics | prompt-engineer; if not wired, tell the user which role should take it | …
Read the whole file at its exact version.
How to install
mdr add oneafrikan/the-grid/agent-factory/roles/context-engineer/AGENTS.md@sha256:80ec1a8985c0a704The line at the top of this page pins the label git:20261021.c1824e3, 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_ywkle5iubu5il36z)
4 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in oneafrikan/the-grid/agent-factory/roles/context-engineer/AGENTS.md since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of AGENTS.md from somewhere else? Ask it: where did my AGENTS.md come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Oct 21, 2026.
Watch this file (sign in, one email per new version)
Installed this file, say at AGENTS.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (3443 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
oneafrikan/the-grid · 5 stars · license MIT · pushed 2026-11-13 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ywkle5iubu5il36z GET https://markdownregistry.com/api/v1/resolve?ref=oneafrikan/the-grid/agent-factory/roles/context-engineer/AGENTS.md GET https://markdownregistry.com/api/v1/blob/80ec1a8985c0a704d0d08439a0e066358ed2c2803218e1d7253a704ccff4f9c1
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.