Borrowing it
Nothing to install: this file belongs to sethclawd-prog/schemaguard. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sethclawd-prog/schemaguard/main/AGENTS.mdgit clone --depth 1 https://github.com/sethclawd-prog/schemaguardWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/sethclawd-prog/schemaguard/agents-md)<a href="https://agentmods.dev/instructions/sethclawd-prog/schemaguard/agents-md"><img src="https://agentmods.dev/badge/instructions/sethclawd-prog/schemaguard/agents-md.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00498 | $0.00498 |
| Opus 5 | $0.00249 | $0.00249 |
| Sonnet 5 | $0.00100 | $0.00100 |
| Haiku 4.5 | $0.00050 | $0.00050 |
Grade B, and why
schemaguard AGENTS.md scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
**Claude Code** (`~/.claude/settings.json`): What it actually says
SchemGuard — Agent Integration Guide
For Claude Code / Codex / OpenClaw / Any MCP-Compatible Agent
MCP Server Setup
Add SchemGuard as a tool server in your agent config:
Claude Code (~/.claude/settings.json):
{
"mcpServers": {
"schemaguard": {
"command": "node",
"args": ["/path/to/node_modules/@sethclawd/schemaguard/mcp-server.js"]
}
}
}
Or project-level (.claude/settings.json in repo root):
{
"mcpServers": {
"schemaguard": {
"command": "npx",
"args": ["@sethclawd/schemaguard", "--mcp"]
}
}
}
Available Tools
Once connected, agents get three tools:
| Tool | When to Use |
|---|---|
schemaguard_diff |
Comparing two OpenAPI specs — shows breaking vs safe changes |
schemaguard_lint |
Validating spec quality — missing fields, security, etc. |
schemaguard_check |
CI-style pass/fail — "is this safe to deploy?" |
Direct CLI Usage (No MCP)
Agents can also shell out directly:
# Diff two specs
npx @sethclawd/schemaguard diff old.yaml new.yaml
# CI check
npx @sethclawd/schemaguard ci --spec ./openapi.yaml --baseline ./baseline.yaml
# Lint
npx @sethclawd/schemaguard lint ./openapi.yaml
# JSON output (machine-readable)
npx @sethclawd/schemaguard diff old.yaml new.yaml --format json
When Should Agents Use This?
- Before committing changes to an OpenAPI spec
- When reviewing PRs that modify API routes
- After generating/updating OpenAPI specs from code
- Before deploying API changes to production
- When validating that a migration maintains backward compatibility
Exit Codes
| Code | Meaning |
|---|---|
| 0 | No breaking changes (safe) |
| 1 | Breaking changes detected (blocked) |
| 2 | Error (invalid spec, file not found) |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 76 lines · 498 tokens per session scan B 699af906a09f
schemaguard AGENTS.md is an instructions file published in the GitHub repository sethclawd-prog/schemaguard (0 stars, last pushed 6mo ago), licensed MIT. It adds 498 tokens to every session, about $0.0025 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
vibe-coding-prompt-template backend.instructions.md
Instructions for KhazP/vibe-coding-prompt-template: Read AGENTS.md, agentdocs/techstack.md, and agentdocs/codepatterns.md.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).