agent-executed · OSPS Baseline inside · policy as YAML
Point a coding agent at AGENTS.md and it audits an existing repository against the OpenSSF OSPS Baseline plus your house policy, or scaffolds a new one to the same standard. The prompt carries no policy: every opinion lives in YAML you can read, diff, and argue with.
The agent prompt: modes, hard rules, phases. Contains no policy.
Pinned Baseline version, profiles, tiers, house merge and review rules, required files.
Per-stack rules: what to check in an existing repo, what to generate in a new one.
# once, as a Claude Code plugin /plugin marketplace add dcotelo/shipshape /plugin install shipshape@shipshape # then, in any repository /shipshape audit /shipshape scaffold
Ask for a dry run and the guarantee is stronger: it reads the tree, the API, and the checklist, then writes nothing to the repository or to GitHub. No file in the tree, no git command that writes, no API call that is not a read. The ruleset it would apply is printed rather than sent, and the report goes to stdout unless you ask for a file, which lands outside the repository. That is how you point it at a mature repository without risking one.
not_run.