bro-check-standards

bro-check-standards is a command for Claude Code from dinnovos/dinnovos-marketplace. It costs 31 tokens per session (7,023 once invoked), scanned A, original, MIT.

A read-only audit command that checks a project's architecture and its compliance with CLAUDE.md and AGENTS.md, files that define instructions for coding assistants.

In plain words
What is it for?
Use it to review the whole project or a selected path, module, or feature against its architecture and coding rules.
Why use it?
It highlights whether code follows the project's documented standards without changing the files.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; mentions CLAUDE.md; positional $N argument.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is 3. Relative imports (./utils, ../hooks).

Part of the bro-code-tools plugin — 8 commands shipped together

Good fit Use it to review the whole project or a selected path, module, or feature against its architecture and coding rules.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/dinnovos/dinnovos-marketplace
agentmods
npx agentmods add commands/dinnovos/dinnovos-marketplace/bro-check-standards

Made for: Claude Code.

Or install bro-code-tools, the plugin that ships this one along with the rest of its 8 commands.

Wrote 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.

agentmods badge for bro-check-standards

README.md
[![agentmods](https://agentmods.dev/badge/commands/dinnovos/dinnovos-marketplace/bro-check-standards/github.svg)](https://agentmods.dev/commands/dinnovos/dinnovos-marketplace/bro-check-standards)
Your own site
<a href="https://agentmods.dev/commands/dinnovos/dinnovos-marketplace/bro-check-standards"><img src="https://agentmods.dev/badge/commands/dinnovos/dinnovos-marketplace/bro-check-standards/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for bro-check-standards

Your own site · 80×15
<a href="https://agentmods.dev/commands/dinnovos/dinnovos-marketplace/bro-check-standards"><img src="https://agentmods.dev/badge/commands/dinnovos/dinnovos-marketplace/bro-check-standards.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 7,023 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00031 $0.07023
Opus 5 $0.00015 $0.03512
Sonnet 5 $0.00006 $0.01405
Haiku 4.5 $0.00003 $0.00702

Measured 12d ago against content hash 7969b537637b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

bro-check-standards 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 12d 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.

plugins/bro-code-tools/commands/bro-check-standards.md · 894 lines

How it starts

The opening of the file, as written. The whole thing — 894 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Architecture and Standards Compliance Audit

Analyze project architecture and validate compliance with established standards in CLAUDE.md and AGENTS.md. Read-only, doesn't modify anything. Multi-language support.

User Input

The user can specify what to audit in various ways:

Exact path:

  • /bro-check-standards src/
  • /bro-check-standards src/modules/payments/
  • /bro-check-standards app/services/

Natural language (illustrative examples):

  • /bro-check-standards check the <module> architecture
  • /bro-check-standards validate <feature> against standards
  • /bro-check-standards audit compliance of <area>
  • /bro-check-standards review if <module> follows the rules

No arguments:

  • /bro-check-standards → audits the entire project

Note: Terms like "authentication", "payments", "users" are just examples. Interpret what the user requests and search for the corresponding files in the project.


Step 1: Interpret the Request

If it's an exact path:

Use directly.

If it's natural language:

Search for files matching the description:

# Explore project structure (all extensions)
find . -type f \( -name "*.ts" -o -name "*.tsx" -o -name "*.js" -o -name "*.jsx" -o -name "*.py" -o -name "*.go" -o -name "*.rs" -o -name "*.php" -o -name "*.rb" -o -name "*.java" -o -name "*.cs" -o -name "*.kt" \) | grep -v node_modules | grep -v vendor | grep -v target | grep -v __pycache__ | grep -v dist | grep -v .git

# Search by related name (replace <term> with what the user requested)
find . -type f -iname "*<term>*" | grep -v node_modules
find . -type d -iname "*<term>*" | grep -v node_modules

# Search related content
grep -ril "<term>" --include="*.ts" --include="*.tsx" --include="*.js" --include="*.py" --include="*.go" --include="*.rs" --include="*.php" | grep -v node_modules | head -20

Confirm with the user if you find multiple matches:

Found these files related to "<term>":
1. src/components/[File1].tsx
2. src/hooks/[File2].ts
3. src/services/[File3].ts

Should I audit all of them or a specific one?

Read the full file on GitHub · 894 lines

Changes

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.

  1. 12d ago First seen · 894 lines · 31 tokens per session scan A 7969b537637b

Subscribe to this mod's changes

bro-check-standards is a command published in the GitHub repository dinnovos/dinnovos-marketplace (2 stars, last pushed 7mo ago), licensed MIT. It adds 31 tokens to every session and 7,023 once invoked, about $0.0002 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.