AGENTS.md@.deepsecA
AGENTS.md@.deepsec from everruns/everruns is an AGENTS.md file: the standing instructions coding agents read in that repo.
mdr add everruns/everruns/.deepsec/AGENTS.md@git:20261003.aaf3bb0Pins git:20261003.aaf3bb0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- AGENTS.md file
- Repository
- everruns/everruns
- Path
.deepsec/AGENTS.md- Versions recorded
- 2
- Latest version
- git:20261003.aaf3bb0, committed Oct 3, 2026
- First version recorded
- May 8, 2026
- Size
- 824 bytes
- Repository stars
- 67
- 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 setup This is a DeepSec scanning workspace. Read `README.md` for the configured project and `node_modules/deepsec/SKILL.md` for commands matching the installed version. The full docs ship at `node_modules/deepsec/dist/docs/`. - For a scan session, check `deepsec setup --status --output json`, then run `deepsec scan` and `deepsec process` from this directory. The process command resumes pending files. - For changes to the target codebase or matcher set, run `deepsec setup` to reconcile the surface inventory and coverage before processing. - For a new project, run `deepsec init-project <root>` and then follow its `data/<id>/SETUP.md` prompt. - Review generated matchers before committing. Write a hand-authored matcher only after a confirmed finding warrants one; read `writing-matchers.md` first.
Read the whole file at its exact version.
How to install
mdr add everruns/everruns/.deepsec/AGENTS.md@sha256:4a4a90dcac0a9ab2The line at the top of this page pins the label git:20261003.aaf3bb0, 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_e4kbxx4iif3xq7si)
2 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 everruns/everruns/.deepsec/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 2 versions of this file, between May 8, 2026 and Oct 3, 2026, about one every 148 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261003.aaf3bb0 latest | 2026-10-03 | aaf3bb0 | 824 B | A | view · diff |
| git:20260508.6dedfb6 | 2026-05-08 | 6dedfb6 | 841 B | A | view |
Copies
1 file in 1 other repository holds the exact bytes of one of this file's versions, each committed after this file had them: it holds an older version.
- marco-trotta1/awesome-agents-md · people/peter-steinberger/deepsec/.deepsec/AGENTS.md · 1 version behind · 5 stars
A copy does not update when this file does. Whoever holds one can learn which version it is with the Check your copy box below, or by asking their agent. Matched on exact bytes and commit dates only.
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 (824 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
everruns/everruns · 67 stars · license MIT · pushed 2026-11-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_e4kbxx4iif3xq7si GET https://markdownregistry.com/api/v1/resolve?ref=everruns/everruns/.deepsec/AGENTS.md GET https://markdownregistry.com/api/v1/blob/4a4a90dcac0a9ab22bea041e36afb9268822390578e65a8a370dc665b5743145
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 everruns/everruns
Every file in everruns/everruns