AGENTS.md@toolsA
AGENTS.md@tools from sfc-gh-eraigosa/dotfiles is an AGENTS.md file: the standing instructions coding agents read in that repo.
mdr add sfc-gh-eraigosa/dotfiles/tools/AGENTS.md@git:20261016.456615cPins git:20261016.456615c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- AGENTS.md file
- Repository
- sfc-gh-eraigosa/dotfiles
- Path
tools/AGENTS.md- Versions recorded
- 1
- Latest version
- git:20261016.456615c, committed Oct 16, 2026
- Size
- 971 bytes
- Repository stars
- 53
- License
- Apache-2.0
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
# tools/ — pinned build modules for repo tooling Go modules that exist only to **build a tool at a pinned version** for a Makefile target. They are not part of the product, are not installed by `install.sh`, and are not scanned or linted as `sdk/` modules (the `sdk/*` loops skip them). | Module | Builds | Used by | Why pinned here | | :-- | :-- | :-- | :-- | | [`security/`](./security/go.mod) | `gosec`, `govulncheck` | `make security` (CI: Security Scan) | a tagged `gosec` vendors an `x/tools` that cannot read the `.go-version` toolchain's export data; requiring `x/tools` explicitly keeps the scan on the same Go as the code | **Bumping:** edit the `require` lines in the module's `go.mod`, run `go mod tidy` inside it, run the Makefile target, commit `go.mod` + `go.sum` together. The policy that those tools enforce lives in the Makefile target's comment block and in [`docs/mbo/designs/security-scan-green.md`](../docs/mbo/designs/security-scan-green.md).
Read the whole file at its exact version.
How to install
mdr add sfc-gh-eraigosa/dotfiles/tools/AGENTS.md@sha256:be0919a252200726The line at the top of this page pins the label git:20261016.456615c, 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_wvzixxg2knfrkxtj)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 16, 2026.
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (971 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
sfc-gh-eraigosa/dotfiles · 53 stars · license Apache-2.0 · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_wvzixxg2knfrkxtj GET https://markdownregistry.com/api/v1/resolve?ref=sfc-gh-eraigosa/dotfiles/tools/AGENTS.md GET https://markdownregistry.com/api/v1/blob/be0919a2522007267cb5c0f86b8a59a61e09693c6fe5f56ec7ec88e1df97ba4e
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.
More from sfc-gh-eraigosa/dotfiles
Every file in sfc-gh-eraigosa/dotfiles