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/agents-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.01867 | $0.01867 |
| Opus 5 | $0.00933 | $0.00933 |
| Sonnet 5 | $0.00373 | $0.00373 |
| Haiku 4.5 | $0.00187 | $0.00187 |
Grade A, and why
regressGuard AGENTS.md scanned grade A 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Verify: `curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=regressguard"`. How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Project Source of Truth
Read RegressGuard-PRD.md before making changes.
The PRD is the product, UX, architecture, and delivery tracker. Section 11 is the implementation source of truth.
Required Workflow
- Pick a task from Section 11.
- Change its status to
IN PROGRESS. - Implement only that task's scope.
- Verify acceptance criteria.
- Record evidence in the PRD or implementation notes.
- Move status to
DONEonly when the Definition of Done is satisfied. - after we features done , create .md document what we have learned why this feature is need . how its used and how it solves problem. this can be used for future reference how product works.
Tech Stack & Dependencies
- Language: Go 1.24+
- CLI Framework: Cobra — command tree, flags, shell completions
- Interactive Prompts: Charm huh — guided
rg initflow (TTY only) - Spinners & Progress: Charm Bubbles + Bubble Tea — phase spinners, route progress tables, elapsed timers
- Terminal Styling: Lip Gloss — color tokens, banners, styled output
- TTY Detection:
mattn/go-isatty+charmbracelet/x/term
Project Structure
cmd/rg/main.go # CLI entry point
internal/
cli/ # Cobra command wiring, help templates
config/ # Config read/write/validation, env var resolution
configrun/ # rg config get/set implementation
checkrun/ # rg check pipeline (load, rerun, diff, render)
doctorrun/ # rg doctor diagnostics
engine/ # Core logic: test runner, route hitter, normalizer, diff
failures/ # Actionable error type (title, cause, next, moreContext)
hookrun/ # rg hook install/uninstall
initrun/ # rg init (interactive + non-interactive)
scanner/ # Project detection, route discovery
snapshot/ # Snapshot read/write
snapshotrun/ # rg snapshot pipeline
state/ # Local state (.regressguard/state.json) — streaks, flags
statusrun/ # rg status quick-glance command
ui/ # Design system tokens, components, animations
style.go # Symbols, colors, MaxWidth, ColorEnabled(), Paint()
theme.go # Lip Gloss style definitions
spinner.go # Reusable phase spinner (braille dots, stderr, TTY-aware)
banner.go # Pass/Warning/Critical banners, celebrations, reveals
components.go # ResultLine, Header, Footer, NextSection, TableHeaderRow
routeprogress.go # Live route progress table (concurrent updates)
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.
- yesterday First seen · 151 lines · 1,867 tokens per session scan A adee4f3b5e0f
regressGuard AGENTS.md is an instructions file published in the GitHub repository Bharath-code/regressGuard (1 stars, last pushed 1mo ago), licensed MIT. It adds 1,867 tokens to every session, about $0.0093 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
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.
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).
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.