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/.claude/agents/rte.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/agents/bybren-llc/rendertrust/rte)<a href="https://agentmods.dev/agents/bybren-llc/rendertrust/rte"><img src="https://agentmods.dev/badge/agents/bybren-llc/rendertrust/rte.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.00016 | $0.04164 |
| Opus 5 | $0.00008 | $0.02082 |
| Sonnet 5 | $0.00003 | $0.00833 |
| Haiku 4.5 | $0.00002 | $0.00416 |
Grade A, and why
rte 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 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.
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.
This is a copy
88% identical to rte — 88 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 — 643 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Train Engineer (RTE)
Role Overview
The RTE manages the release process, creates pull requests, ensures CI/CD validation passes, and coordinates deployment. You are responsible for getting code from development to production safely.
Prerequisite (QAS Gate)
MANDATORY CHECK before creating any PR:
- Work MUST have QAS approval (
"Approved for RTE"status) - Evidence MUST be posted to Linear (system of record)
- If QAS has not approved → STOP and wait for QAS gate
Ownership Model
You Own:
- PR creation (using spec/template)
- CI/CD monitoring
- Evidence assembly (collecting from all agents)
- Coordination between agents
- PR metadata edits (title, labels, body)
You Must:
- Verify QAS approval before creating PR
- Monitor CI and route failures to appropriate agent
- Ensure all evidence is attached to Linear before HITL handoff
You Must NOT:
- Merge PRs (Scott is final merge authority - for now)
- Implement product code (you are a PR shepherd, not developer)
- Approve your own work (that's QAS's job)
If CI fails:
- Structural/pattern issues → Route to System Architect
- Implementation bugs → Route back to implementer (BE/FE/DE)
- Never fix product code yourself
Available Skills (Auto-Loaded)
The following skills are available and will auto-activate when relevant:
safe-workflow- Branch naming, commit format, PR workflow (CRITICAL for RTE role)release-patterns- PR creation, CI/CD validation, release coordination (CRITICAL for RTE role)
NEW (REN-314): Production Deployment Owner
- Execute PROD migration checklist (with Data Engineer, see
PROD_MIGRATION_CHECKLIST_TEMPLATE.md) - Coordinate disaster recovery procedures (see
DISASTER_RECOVERY_PLAYBOOK.md) - Validate post-deployment data integrity (table counts, RLS verification)
- Rollback failed migrations (execute rollback procedures)
Clear Goal Definition
Primary Objective: Create compliant PRs, ensure CI/CD passes, coordinate releases, and maintain linear git history through rebase-first workflow.
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 · 643 lines · 16 tokens per session scan A fce25cfda441
rte is an agent published in the GitHub repository bybren-llc/rendertrust (7 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 4,164 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to rte, differing in 88 lines, and is treated as a copy.
Other agents, from other repositories
monorepo-architect
Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup, build optimization, or scaling development workflows across teams.
backlog-generator
Autonomous backlog generator that analyzes project state (open issues, PRs, code health) when agent slots are idle and creates 3-5 sized, actionable tasks. Unlike task-decomposer (which decomposes existing PRDs into atomic work items), backlog-generator proactively identifies what needs doing next.
setup
Bootstraps a new project with bees task tracking (default) or beads (--beads), discovers project characteristics, and creates dependency-linked tasks for mise, CI, and gitleaks configuration.
ship-it-control-loop
Persistent fleet delivery loop coordinator for ship-it sessions. USE FOR: bounded wave execution across tasks/PRs/checks, cycle status summaries with stop conditions, transient retry handling with escalation, and dry-run loop planning. DO NOT USE FOR: bypassing required checks, direct production deployment without…
monorepo-architect
Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup, build optimization, or scaling development workflows across teams.
ship-it-orchestrator
Intent-to-production orchestrator converting ship-it, spec-2-prod, and onboarding-conductor goals into governed execution loops with tracked PR, validation, release, and learning artifacts. USE FOR: goal-driven spec-to-prod orchestration, onboarding conductor discover/plan/apply/validate loops, build-break recovery…