AGENTS.mdA
AGENTS.md from jdtzmn/port is an AGENTS.md file: the standing instructions coding agents read in that repo.
mdr add jdtzmn/port/AGENTS.md@git:20260206.b5f9250Pins git:20260206.b5f9250 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- AGENTS.md file
- Repository
- jdtzmn/port
- Path
AGENTS.md- Versions recorded
- 2
- Latest version
- git:20260206.b5f9250, committed Feb 6, 2026
- First version recorded
- Feb 6, 2026
- Size
- 1,327 bytes
- Repository stars
- 11
- 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 This project uses **bd** (beads) for issue tracking. Run `bd onboard` to get started. ## Quick Reference ```bash bd ready # Find available work bd show <id> # View issue details bd update <id> --status in_progress # Claim work bd close <id> # Complete work bd sync # Sync with git ``` ## Landing the Plane (Session Completion) **When ending a work session**, you MUST complete ALL steps below. Work is NOT complete until `git push` succeeds. **MANDATORY WORKFLOW:** 1. **File issues for remaining work** - Create issues for anything that needs follow-up 2. **Run quality gates** (if code changed) - Tests, linters, builds 3. **Update issue status** - Close finished work, update in-progress items 4. **PUSH TO REMOTE** - This is MANDATORY: ```bash git pull --rebase bd sync git push git status # MUST show "up to date with origin" ``` 5. **Clean up** - Clear stashes, prune remote branches 6. **Verify** - All changes committed AND pushed 7. **Hand off** - Provide context for next session **CRITICAL RULES:** - Work is NOT complete until `git push` succeeds …
Read the whole file at its exact version.
How to install
mdr add jdtzmn/port/AGENTS.md@sha256:d5ce327968e3fa85The line at the top of this page pins the label git:20260206.b5f9250, 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_p7u4krgsm5smzncf)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Feb 6, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260206.b5f9250 latest | 2026-02-06 | b5f9250 | 1,327 B | A | view · diff |
| git:20260206.b8de049 | 2026-02-06 | b8de049 | 1,327 B | A | view |
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (1327 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
jdtzmn/port · 11 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_p7u4krgsm5smzncf GET https://markdownregistry.com/api/v1/resolve?ref=jdtzmn/port/AGENTS.md GET https://markdownregistry.com/api/v1/blob/d5ce327968e3fa85b73cc3f8dd612daa63c5a4f80650359ec7beb2abb72c62ce
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.