Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/bharath-code/regressguard/claude-mdgit clone --depth 1 https://github.com/Bharath-code/regressGuardWhat 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 | $0.00784 | $0.00784 |
| Opus 5 | $0.00392 | $0.00392 |
| Sonnet 5 | $0.00157 | $0.00157 |
| Haiku 4.5 | $0.00078 | $0.00078 |
Grade A, and why
regressGuard CLAUDE.md scanned grade A with 0 findings 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 2d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — RegressGuard
One-line: a single-binary Go CLI that records a known-good API baseline and blocks commits when an AI agent silently regresses it. Also an MCP server so the agent can verify its own work.
Read first
AGENTS.md— workflow, tech stack, project structure, CLI/UX/error/test conventions.RegressGuard-PRD.mdSection 11 — implementation source of truth (task tracker).docs/staff-review-2026-06.md— current product review, verdict, and prioritized task breakdown with acceptance criteria.
AGENTS.md rules apply in full; this file does not restate them. On conflict, the PRD
and AGENTS.md win.
Product verdict (2026-06-15): PURSUE (conditional)
Real, well-evidenced problem; high build quality; unique wedge = agent-native verification via MCP. Gated on three conditions before growth spend:
- Eliminate transient-error false positives (trust is the whole product).
- Calm-by-default UX (animations opt-in, instant default).
- Harden + test the MCP path; make the open-core/monetization story real.
Current priorities (see docs/staff-review-2026-06.md for acceptance criteria)
- ✅ Done: P0 transient-error FP, P0 secret hygiene (verified), P1-2 MCP hardening + tests,
P1-1 calm-by-default UX (animations opt-in via
--celebrate), P1-3 scoring-semantics docs- warning-only routes excluded from "unchanged" count, P2-1 open-core positioning +
docs/json-contract.md+docs/paid-layer-spec.md.
- warning-only routes excluded from "unchanged" count, P2-1 open-core positioning +
- P2-2 (spec only, per AGENTS.md scope) — FastAPI/Django route-discovery spec for
scanner, gated behind PRD change-control before any code.
Architecture quick map
internal/engine— test runner, route hitter, schema normalizer, diff (severity rules).internal/checkrun—rg checkpipeline (load snapshot, rerun, diff, render).internal/snapshot— baseline read/write + HMAC integrity + field redaction.internal/mcprun— exposes snapshot/check/status as MCP tools (strategic differentiator).internal/ui— design system; all color viaui.Paint(), animations TTY-only.
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.
- 2d ago First seen · 55 lines · 784 tokens per session scan A 116b4220fca0
regressGuard CLAUDE.md is an instructions file published in the GitHub repository Bharath-code/regressGuard (1 stars, last pushed 1mo ago), licensed MIT. It adds 784 tokens to every session, about $0.0039 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.