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/bybren-llc/safe-agentic-workflow/claude-mdgit clone --depth 1 https://github.com/bybren-llc/safe-agentic-workflowWrote 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/bybren-llc/safe-agentic-workflow/claude-md)<a href="https://agentmods.dev/instructions/bybren-llc/safe-agentic-workflow/claude-md"><img src="https://agentmods.dev/badge/instructions/bybren-llc/safe-agentic-workflow/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.01672 | $0.01672 |
| Opus 5 | $0.00836 | $0.00836 |
| Sonnet 5 | $0.00334 | $0.00334 |
| Haiku 4.5 | $0.00167 | $0.00167 |
Grade A, and why
safe-agentic-workflow 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
AI Assistant Context for SAFe Multi-Agent Development
Repository: {{PROJECT_NAME}} Methodology: SAFe (Scaled Agile Framework) Agentic Workflow Philosophy: "Round Table" - Equal voice, mutual respect, shared responsibility
Quick Start
This is a SAFe multi-agent development project with 11 specialized AI agents working collaboratively. You are part of a team where your input has equal weight with human contributors.
Core Principles:
- Search for existing patterns before creating new ones ("Search First, Reuse Always")
- Attach evidence to Linear tickets for all work
- You have "stop-the-line" authority for architectural/security concerns
- Follow SAFe methodology: Epic → Feature → Story → Enabler
Key Resources:
- AGENTS.md - All 11 agent roles, invocation patterns, capabilities
- CONTRIBUTING.md - Git workflow, commit standards, PR process
- docs/onboarding/ - Setup guides and daily workflows
- docs/guides/ROUND-TABLE-PHILOSOPHY.md - Collaboration principles
- patterns_library/ - Reusable code patterns (18+ patterns, 7 categories)
- knowledge-vault/ - Evidence-verified knowledge base. To build this repo's own vault, run SAW-VAULT-BUILD.md
Development Commands
# Development server
{{DEV_COMMAND}} # Start development server
# Build and production
{{BUILD_COMMAND}} # Build for production
{{START_COMMAND}} # Start production server
# Code quality
{{LINT_COMMAND}} # Run linting
{{LINT_FIX_COMMAND}} # Auto-fix linting issues
{{TYPE_CHECK_COMMAND}} # TypeScript validation
{{FORMAT_CHECK_COMMAND}} # Prettier formatting check
# Testing
{{TEST_UNIT_COMMAND}} # Run unit tests
{{TEST_INTEGRATION_COMMAND}} # Run integration tests
{{TEST_E2E_COMMAND}} # Run end-to-end tests
# Database (if applicable)
{{DB_MIGRATE_COMMAND}} # Run migrations
# CI/CD validation (REQUIRED before PR)
{{CI_VALIDATE_COMMAND}} # Run all quality checks
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 · 205 lines · 1,672 tokens per session scan A 568e6d43732f
safe-agentic-workflow CLAUDE.md is an instructions file published in the GitHub repository bybren-llc/safe-agentic-workflow (406 stars, last pushed 1mo ago), licensed MIT. It adds 1,672 tokens to every session, about $0.0084 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-09-03.
Other instructions, from other repositories
framework AGENTS.md
AGENTS.md instructions for ai-driven-dev/framework, covering agents.md, behavior, communication, action and memory management.
claude-code-templates CLAUDE.md
Claude Code instructions for Justdvp/claude-code-templates, covering claude.md, project overview, development commands, package management and application commands.
trellis AGENTS.md
Instructions for craigcossairt/trellis, covering agents.md , project, what i need from agents, current state - source of truth pointers and tech stack.
speckit AGENTS.md
AGENTS.md instructions for jmanhype/speckit, covering agents.md - instructions for ai coding agents, core philosophy, pivotal methodology alignment, pivotal-style epic format and priority levels (pivotal-aligned).
Agentic-Ground-Rules GEMINI.md
Gemini CLI instructions for criger/Agentic-Ground-Rules, a project described as: Model-agnostic AGENTS.md templates and project instructions for AI coding agents such as Codex, Claude Code and Gemini CLI.
butgo-specdrive-lab AGENTS.md
AGENTS.md instructions for butgo/butgo-specdrive-lab, covering agents.md, 1. 문서 목적, 2. 프로젝트 성격, 3. 적용 범위 and 4. 문서 계층 원칙.