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
# AGENTS.md
See `CLAUDE.md` for the full architecture overview (plugin structure, frameworks, connectors, and the Finding data contract). This file captures durable, non-obvious notes for coding agents working in this repo.
## Repo shape
This repo is a Claude Code plugin marketplace: mostly Markdown/YAML/JSON plugin content, plus a root Node.js (ESM) toolkit of CLI scripts, a schema/contract test suite, and a few independent React/Vite apps. There is no backend service or database; "running the app" means running the Node CLI scripts, the test suite, the optional local dashboard server, and/or the Vite frontends.
## Setup, tests, and checks
- Runtime: Node.js (CI pins Node 20; Node 22 works). Single `npm install` at the repo root installs all toolkit + test deps. There are no committed lockfiles, so installs resolve latest within semver ranges.
…
The line at the top of this page pins the label git:20260807.38ef6f3, 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.
GET https://markdownregistry.com/api/v1/artifacts/art_cy6h2hiofq3c3zhv
GET https://markdownregistry.com/api/v1/resolve?ref=grcengclub/claude-grc-engineering/AGENTS.md
GET https://markdownregistry.com/api/v1/blob/87a92af255759169562819e653c9022d57c921aed105412d9e205548b67af9b7
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.
grcengclub/claude-grc-engineering · plugins/academic-research-companion/skills/academic-research-companion/SKILL.md · Guide a research project through the full academic lifecycle — from raw idea to concrete research question, literature…
grcengclub/claude-grc-engineering · plugins/connectors/aws-inspector/skills/aws-inspector-expert/SKILL.md · Expertise in evaluating AWS accounts for compliance — what checks are meaningful, which SCF controls they map to, and…
grcengclub/claude-grc-engineering · plugins/connectors/aws-secrets-inspector/skills/aws-secrets-inspector-expert/SKILL.md · Use when interpreting AWS Secrets Manager connector output, deciding between inspector and retrieve modes, drafting…
grcengclub/claude-grc-engineering · plugins/connectors/azure-inspector/skills/azure-inspector-expert/SKILL.md · Expertise in evaluating Azure subscription findings from azure-inspector and mapping them to SCF controls.
grcengclub/claude-grc-engineering · plugins/connectors/gcp-inspector/skills/gcp-inspector-expert/SKILL.md · Expertise in evaluating GCP projects for compliance — what checks are meaningful, which SCF controls they map to, and…
grcengclub/claude-grc-engineering · plugins/connectors/github-inspector/skills/github-inspector-expert/SKILL.md · Expertise in evaluating GitHub repositories for compliance — what checks are meaningful, which SCF controls they map…
