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/agents-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/agents-md)<a href="https://agentmods.dev/instructions/bybren-llc/safe-agentic-workflow/agents-md"><img src="https://agentmods.dev/badge/instructions/bybren-llc/safe-agentic-workflow/agents-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 | $0.04216 | $0.04216 |
| Opus 5 | $0.02108 | $0.02108 |
| Sonnet 5 | $0.00843 | $0.00843 |
| Haiku 4.5 | $0.00422 | $0.00422 |
Grade B, and why
safe-agentic-workflow AGENTS.md scanned grade B 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
grep -l "file_path" ~/.claude/todos/*.json How it starts
The opening of the file, as written. The whole thing — 450 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SAFe Agent Team Quick Reference
Philosophy: "Search First, Reuse Always, Create Only When Necessary"
Pattern discovery is MANDATORY before implementation.
Team Culture: "We work as a round table team that has 4 pillars of SAFe inscribed on that round table. It means something."
Documentation
Workflow SOPs:
- Agent Workflow SOP v1.4 - vNext contract, Exit States, Role Collapsing ({{TICKET_PREFIX}}-497/499)
- Agent Configuration SOP - Tool restrictions, model selection
- ARCHitect-in-CLI Role - Primary orchestrator definition
CI/CD Documentation:
- CI/CD Pipeline Guide - Pipeline implementation guide
Database SOPs:
- RLS Migration SOP - MANDATORY for Data Engineer
Project Standards:
- Harness Whitepapers - Architecture, research alignment, and evidence
- Agent Perspective - Why the harness works
- SAFe Methodology - This repository
When to Use Which Agent
| Agent Role | Use Case | Success Criteria | Primary Tools |
|---|---|---|---|
| TDM (Technical Delivery Manager) | Reactive blocker resolution, Linear updates, evidence tracking (NOT orchestration - see v1.3 SOP) | Blockers resolved, evidence attached, Linear updated | Linear, Confluence |
| BSA (Business Systems Analyst) | Requirements decomposition, acceptance criteria, testing strategy | Clear user stories, testable ACs, QA plan defined | Linear, Confluence, Markdown |
| System Architect | Pattern validation, Stage 1 PR review, migration approval, architectural decisions | ADR created, PR technical review complete, no conflicts | Read, Grep, ADR templates |
| FE Developer | UI components, client-side logic, user interactions | Lint and build passes | Read, Write, Edit, Bash |
| BE Developer | API routes, server logic, RLS enforcement | Integration tests pass | Read, Write, Edit, Bash |
| DE (Data Engineer) | Schema changes, migrations, database architecture | Migration applied, RLS maintained | Prisma, SQL, migration tools |
| TW (Technical Writer) | Documentation, guides, technical content | Markdown lint passes | Read, Write, Edit, Grep, Glob, Bash |
| DPE (Data Provisioning Engineer) | Test data, database access, data validation | Test data available, DB accessible | SQL, Prisma Studio, scripts |
| QAS (Quality Assurance) | GATE OWNER: Execute testing, validate ACs, iteration authority, evidence to Linear | All ACs verified, evidence posted, Exit: "Approved for RTE" | Playwright, Jest, Linear MCP |
| SecEng (Security Engineer) | Security validation, RLS checks, vulnerability assessment (Independence Gate - not collapsible) | Security audit passed, RLS enforced | RLS scripts, security tools |
| RTE (Release Train Engineer) | PR SHEPHERD: PR creation, CI/CD monitoring (NO code, NO merge) - Exit: "Ready for HITL" | PR created, CI green, Exit: "Ready for HITL Review" | Git, GitHub CLI, CI tools |
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 · 450 lines · 4,216 tokens per session scan B c2ea75893ae9
safe-agentic-workflow AGENTS.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 4,216 tokens to every session, about $0.0211 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other instructions, from other repositories
Spec-Flow CLAUDE.md
Claude Code instructions for marcusgoll/Spec-Flow, covering claude.md, what this is, why this approach works, how to use it and quick start.
Spec-Flow GEMINI.md
Gemini CLI instructions for marcusgoll/Spec-Flow, covering gemini.md - spec-flow for gemini cli, what this is, your role, how to use it (for the model) and command map.
Spec-Flow AGENTS.md
AGENTS.md instructions for marcusgoll/Spec-Flow, covering spec-flow agents, shared brain, tool boundaries and hard rules.
speckit CLAUDE.md
Claude Code instructions for jmanhype/speckit, covering claude.md, repository structure, directory layout, pivotal labs methodology and pivotal-style beads workflow.
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).
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.