Borrowing it
Nothing to install: this file belongs to bybren-llc/rendertrust. 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/bybren-llc/rendertrust/dev/AGENTS.mdgit clone --depth 1 https://github.com/bybren-llc/rendertrustWrote 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/rendertrust/agents-md)<a href="https://agentmods.dev/instructions/bybren-llc/rendertrust/agents-md"><img src="https://agentmods.dev/badge/instructions/bybren-llc/rendertrust/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.1 | $0.04103 | $0.04103 |
| Opus 5 | $0.02051 | $0.02051 |
| Sonnet 5 | $0.00821 | $0.00821 |
| Haiku 4.5 | $0.00410 | $0.00410 |
Grade B, and why
rendertrust 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 This is a copy
92% identical to safe-agentic-workflow AGENTS.md — 70 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 442 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 (REN-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 Whitepaper - Complete harness architecture
- 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 | SQLAlchemy, Alembic, SQL |
| 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, pgAdmin, scripts |
| QAS (Quality Assurance) | GATE OWNER: Execute testing, validate ACs, iteration authority, evidence to Linear | All ACs verified, evidence posted, Exit: "Approved for RTE" | pytest, Playwright, 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 · 442 lines · 4,103 tokens per session scan B aae80e4ecd9f
rendertrust AGENTS.md is an instructions file published in the GitHub repository bybren-llc/rendertrust (7 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 4,103 tokens to every session, about $0.0205 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). It is 92% identical to safe-agentic-workflow AGENTS.md, differing in 70 lines, and is treated as a copy.
Other instructions, from other repositories
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.
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).
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).
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.
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.