explaingit

anmoln7/agent-standard-oss

Analysis updated 2026-05-18

5ShellAudience · developerComplexity · 2/5LicenseSetup · easy

TLDR

A convention and toolset for keeping AI agent instruction files (AGENTS.md, CLAUDE.md) accurate and single-sourced across a codebase, with anti-drift contracts, a fix log, and safe commit helpers.

Mindmap

mindmap
  root((agent-standard-oss))
    What it does
      Single-sources instruction files
      Prevents drift between files
      Logs past bugs and gotchas
      Checks compliance via CI
    Core conventions
      AGENTS.md is canonical
      CLAUDE.md points to it
      docs/solutions fix log
      Keep in sync blocks
    Optional automation
      Pre-commit secret scan
      SessionStart self-healing hooks
      Safe commit helpers
      Multi-account deploy guard
    Adoption
      Docs-only lane
      Interactive adopt wizard
      Claude Code plugin
    Audience
      AI-assisted dev teams
      Solo developers using agents
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Consolidate a project's CLAUDE.md and AGENTS.md into a single canonical file so AI agents always read accurate guidance.

USE CASE 2

Build a searchable log of past bugs and gotchas in docs/solutions/ so AI agents do not repeat the same mistakes across sessions.

USE CASE 3

Add a pre-commit secret scan and session startup hooks to a repository where multiple AI agents are making commits.

What is it built with?

ShellBashGitClaude CodeMarkdown

How does it compare?

anmoln7/agent-standard-osstrivo25/code-airlockchrisor-dev/claude-autosync
Stars572
LanguageShellShellShell
Setup difficultyeasyhardmoderate
Complexity2/53/53/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min

Docs-only adoption requires only cloning the repo and renaming files, automated features optionally add shell scripts and git hooks.

MIT, free to use, modify, and distribute for any purpose including commercial.

In plain English

Agent Standard is a convention for keeping the instruction files that AI coding agents read, usually named AGENTS.md or CLAUDE.md, accurate and up to date as a codebase changes. These files tell agents how to work in a repository: what commands to run, what rules to follow, what pitfalls to avoid. The problem the project addresses is that these files drift. When a codebase has two instruction files, or when a README also documents some of the same rules, they fall out of sync and the agent starts following stale guidance confidently. The core of the standard is a small set of conventions. One file, AGENTS.md, is the single authoritative source. If you also have CLAUDE.md (the file Claude Code reads), it becomes a one-line reference pointing at AGENTS.md. A docs/solutions/ directory holds a separate file for each past bug or gotcha the team has encountered, making it searchable. A designated section in the main instruction file lists file pairs that must always agree, creating an explicit anti-drift contract that can be checked automatically. Beyond the documentation conventions, the project includes optional shell scripts and hooks for safer day-to-day work with AI agents: a pre-commit scan for secrets, session startup hooks that silently repair common configuration failures before they cause problems, commit identity rules, helpers for safe landing of changes, and a multi-account deploy guardrail. Adoption comes in layers. The docs-only approach requires no scripts and no automation: clone the repo, rename your instruction file, create the fix log directory, and run a read-only check. The fuller adoption adds shell scripts to your PATH and optional git hooks. An interactive wizard called adopt guides you through either path with a before-and-after scorecard and a question before every change. Nothing is deleted automatically. The standard works with Claude Code, Codex, Cursor, and Gemini. The AGENTS.md file is the format those tools read natively. A Claude Code plugin wraps the wizard in a slash command. The project is MIT licensed and includes a CI action that checks compliance automatically.

Copy-paste prompts

Prompt 1
I have both a CLAUDE.md and an AGENTS.md in my repo and they are out of sync. How does agent-standard-oss help me consolidate them and what is the recommended file structure?
Prompt 2
I want to add a docs/solutions entry for a bug my AI agent keeps repeating. What does the frontmatter format look like and how does the agent find these files?
Prompt 3
Walk me through the docs-only adoption path for agent-standard-oss that installs no hooks or scripts and just sets up the instruction file structure and compliance check.

Frequently asked questions

What is agent-standard-oss?

A convention and toolset for keeping AI agent instruction files (AGENTS.md, CLAUDE.md) accurate and single-sourced across a codebase, with anti-drift contracts, a fix log, and safe commit helpers.

What language is agent-standard-oss written in?

Mainly Shell. The stack also includes Shell, Bash, Git.

What license does agent-standard-oss use?

MIT, free to use, modify, and distribute for any purpose including commercial.

How hard is agent-standard-oss to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is agent-standard-oss for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Scan in gitsafehub Deploy in gitdeployhub anmoln7 on gitmyhub

Verify against the repo before relying on details.