Borrowing it
Nothing to install: this file belongs to robertguss/bmad_automated. 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/robertguss/bmad_automated/main/CLAUDE.mdgit clone --depth 1 https://github.com/robertguss/bmad_automatedWrote 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/robertguss/bmad_automated/claude-md)<a href="https://agentmods.dev/instructions/robertguss/bmad_automated/claude-md"><img src="https://agentmods.dev/badge/instructions/robertguss/bmad_automated/claude-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.00512 | $0.00512 |
| Opus 5 | $0.00256 | $0.00256 |
| Sonnet 5 | $0.00102 | $0.00102 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
bmad_automated 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 8d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Build & Development Commands
just build # Build binary to ./bmad-automate
just test # Run all tests
just test-verbose # Run tests with verbose output
just test-pkg ./internal/claude # Test specific package
just test-coverage # Generate coverage.html
just lint # Run golangci-lint
just check # Run fmt, vet, and test
just run --help # Build and run with arguments
Architecture
This is a CLI tool that orchestrates Claude CLI to run automated development workflows. It spawns Claude as a subprocess, parses its streaming JSON output, and displays formatted results.
Package Dependencies
cmd/bmad-automate/main.go
│
▼
internal/cli (Cobra commands)
│
├──► internal/workflow (orchestration)
│ │
│ ├──► internal/claude (Claude execution + JSON parsing)
│ └──► internal/output (terminal formatting)
│
└──► internal/config (Viper configuration)
Key Interfaces for Testing
claude.Executor- Interface for running Claude CLI. UseMockExecutorin tests to avoid spawning real processes.output.Printer- Interface for terminal output. UseNewPrinterWithWriter(buf)to capture output in tests.
Data Flow
- CLI command receives story key
config.Config.GetPrompt()expands Go template with{{.StoryKey}}workflow.Runnercallsclaude.Executor.ExecuteWithResult()claude.Parserreads streaming JSON, emitsEventstructsoutput.Printerformats and displays events
Configuration
Workflow prompts are in config/workflows.yaml using Go templates. Config loads via Viper with env var overrides (BMAD_ prefix).
Claude CLI Integration
The executor always passes --dangerously-skip-permissions and --output-format stream-json. Each JSON line from stdout is parsed into StreamEvent structs, then converted to the higher-level Event type with convenience methods (IsText(), IsToolUse(), IsToolResult()).
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.
- 8d ago First seen · 58 lines · 512 tokens per session scan A 5ac50b70103a
bmad_automated CLAUDE.md is an instructions file published in the GitHub repository robertguss/bmad_automated (88 stars, last pushed 8mo ago), licensed MIT. It adds 512 tokens to every session, about $0.0026 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-30.
Other instructions, from other repositories
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).
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.