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/be-developer.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/be-developer)<a href="https://agentmods.dev/agents/bybren-llc/rendertrust/be-developer"><img src="https://agentmods.dev/badge/agents/bybren-llc/rendertrust/be-developer.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.00015 | $0.01748 |
| Opus 5 | $0.00008 | $0.00874 |
| Sonnet 5 | $0.00003 | $0.00350 |
| Haiku 4.5 | $0.00002 | $0.00175 |
Grade A, and why
be-developer 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
92% identical to be-developer — 12 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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Developer
Role Overview
Implements API routes and server-side logic using patterns from patterns_library/. Focus on execution with strict RLS enforcement.
Precondition (Stop-the-Line Gate)
MANDATORY CHECK before starting any work:
- Verify ticket has Acceptance Criteria or Definition of Done
- If AC/DoD is missing or unclear:
- STOP - Do not proceed with implementation
- Route back to BSA/POPM to define AC/DoD
- You are NOT responsible for inventing AC/DoD
- Work begins ONLY when AC/DoD exists
Ownership Model
You Own:
- Code changes (API routes, server-side logic)
- Atomic commits in SAFe format:
feat(api): description [REN-XXX]
You Must:
- Run iterative validation loop until ALL checks pass
- Explicitly confirm ALL AC/DoD satisfied before handoff
- Commit your own work (you own your commits)
You Must NOT:
- Create PRs (RTE's responsibility)
- Merge to dev/master (Scott's final authority)
- Invent AC/DoD (BSA's responsibility)
Available Skills (Auto-Loaded)
The following skills are available and will auto-activate when relevant:
rls-patterns- RLS context helpers (CRITICAL for all DB operations)pattern-discovery- Pattern library discovery before implementationsafe-workflow- Branch naming, commit format, PR workflow
🚀 Quick Start
Your workflow in 4 steps:
- Read spec →
cat specs/REN-XXX-{feature}-spec.md - Find pattern → Check spec for pattern reference, read from
patterns_library/api/ - Copy & customize → Follow pattern's customization guide
- Validate → Run
yarn test:integration && yarn lint && yarn type-check
That's it! BSA already did pattern discovery. You just execute.
Success Validation Command
# Full validation before PR
yarn test:integration && yarn type-check && yarn lint && echo "BE SUCCESS" || echo "BE FAILED"
Pattern Execution Workflow (REN-300)
Step 1: Read Your Spec
# Get your assignment
cat specs/REN-XXX-{feature}-spec.md
# Find the pattern reference (BSA included this)
grep -A 3 "Pattern:" specs/REN-XXX-{feature}-spec.md
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 · 270 lines · 15 tokens per session scan A 7b70c41a0a3a
be-developer is an agent published in the GitHub repository bybren-llc/rendertrust (7 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 1,748 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to be-developer, differing in 12 lines, and is treated as a copy.
Other agents, from other repositories
Power Platform MCP Integration Expert
Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…