AGENTS.md@examples/nasde-dev-skill/variants/codex-nasde-dev-with-archA
AGENTS.md@examples/nasde-dev-skill/variants/codex-nasde-dev-with-arch from noesisvision/nasde-toolkit is an AGENTS.md file: the standing instructions coding agents read in that repo.
mdr add noesisvision/nasde-toolkit/examples/nasde-dev-skill/variants/codex-nasde-dev-with-arch/AGENTS.md@git:20260610.cf306c9Pins git:20260610.cf306c9 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- AGENTS.md file
- Repository
- noesisvision/nasde-toolkit
- Path
examples/nasde-dev-skill/variants/codex-nasde-dev-with-arch/AGENTS.md- Versions recorded
- 1
- Latest version
- git:20260610.cf306c9, committed Jun 10, 2026
- Size
- 636 bytes
- Repository stars
- 14
- 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
# Agent Instructions ## Approach 1. Begin by consulting the **nasde-dev** skill and apply its guidance throughout this task. 2. Before writing any code, explore the existing codebase to understand its architecture and conventions. 3. Follow existing architectural patterns exactly — match naming, namespaces, directory structure, and code style. 4. When modifying nasde-toolkit functionality (CLI, runner, evaluator, config, agents), follow the `nasde-dev` skill's verification protocol, including documentation sync requirements. 5. After making changes, verify documentation is consistent (CLAUDE.md, README.md, ARCHITECTURE.md).
Read the whole file at its exact version.
How to install
mdr add noesisvision/nasde-toolkit/examples/nasde-dev-skill/variants/codex-nasde-dev-with-arch/AGENTS.md@sha256:3013aa2060b1368eThe line at the top of this page pins the label git:20260610.cf306c9, 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_kp5ad7l5tjjvsjjk)
6 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jun 10, 2026.
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (636 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
noesisvision/nasde-toolkit · 14 stars · license MIT · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kp5ad7l5tjjvsjjk GET https://markdownregistry.com/api/v1/resolve?ref=noesisvision/nasde-toolkit/examples/nasde-dev-skill/variants/codex-nasde-dev-with-arch/AGENTS.md GET https://markdownregistry.com/api/v1/blob/3013aa2060b1368e431295eae7c2be9a37e10295174e52e67df035c6a8b8d15c
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.