AGENTS.md@opt/etcA
AGENTS.md@opt/etc 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/opt/etc/AGENTS.md@git:20261018.31eb401Pins git:20261018.31eb401 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
opt/etc/AGENTS.md- Versions recorded
- 4
- Latest version
- git:20261018.31eb401, committed Oct 18, 2026
- First version recorded
- Aug 31, 2026
- Size
- 3,349 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
# opt/etc — tracked system configuration files Configuration that a script **copies into a system or user location**, kept in the repo as the single source of truth. Nothing here is read from this path at runtime (except `fleet/`, below); nothing here is symlinked into place. **Edit the file here, then re-run its installer.** The deployed copies are overwritten on every install, so a hand-edit to `/etc/...` is always lost. ## `fleet/` — the tracked team plan for `fleet update` `fleet.yaml` is read **in place** from the local dotfiles clone (`<--repo>/opt/etc/fleet/fleet.yaml`) when `gff set fleet.update.config repo` is set — the one exception to "nothing here is read at runtime", because a plan is executable config and copying it would hide which commit it came from. Schema and semantics: [sdk/fleet/README.md](../../sdk/fleet/README.md#fleet-update-host). ## `htop/` — the dotfiles htop view Deployed by [`opt/scripts/system/install_htop.sh`](../scripts/system/install_htop.sh) (gff `install.tools.htop-fit`; flag off removes all three and returns htop to its defaults). | File | Deployed to | Purpose | | :-- | :-- | :-- | …
Read the whole file at its exact version.
How to install
mdr add sfc-gh-eraigosa/dotfiles/opt/etc/AGENTS.md@sha256:a68d953c2d1a2561The line at the top of this page pins the label git:20261018.31eb401, 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_xoly44hrklumtyjb)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Aug 31, 2026 and Oct 18, 2026, about one every 16 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261018.31eb401 latest | 2026-10-18 | 31eb401 | 3,349 B | A | view · diff |
| git:20261017.7496e81 | 2026-10-17 | 7496e81 | 3,153 B | A | view · diff |
| git:20260905.5f0f047 | 2026-09-05 | 5f0f047 | 2,344 B | A | view · diff |
| git:20260831.5a9e62b | 2026-08-31 | 5a9e62b | 1,872 B | A | view |
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (3349 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_xoly44hrklumtyjb GET https://markdownregistry.com/api/v1/resolve?ref=sfc-gh-eraigosa/dotfiles/opt/etc/AGENTS.md GET https://markdownregistry.com/api/v1/blob/a68d953c2d1a2561fd6e854f118e6d821d45c07d430762aa5dd8e93037f20ba7
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.