rendertrust: Agent for Claude Code

.claude/agents/fe-developer.md

fe-developer is an agent for Claude Code from bybren-llc/rendertrust. It costs 11 tokens per session (1,490 once invoked), scanned A, original, Apache-2.0.

A frontend developer role for implementing user-interface code from existing patterns. It requires clear acceptance criteria, which are the conditions that define when work is complete.

In plain words
What is it for?
It helps build UI components, pages, and client-side logic, then check the work against the stated completion criteria.
Why use it?
It prevents implementation from starting with unclear requirements and sets boundaries for coding, validation, commits, and handoff.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is bybren-llc/rendertrust's own configuration. It tells Claude Code how to work on rendertrust itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything rendertrust configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/bybren-llc/rendertrust/dev/.claude/agents/fe-developer.md
Clone the repo
git clone --depth 1 https://github.com/bybren-llc/rendertrust

Made for: Claude Code.

Wrote 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.

agentmods badge for fe-developer

README.md
[![agentmods](https://agentmods.dev/badge/agents/bybren-llc/rendertrust/fe-developer.svg)](https://agentmods.dev/agents/bybren-llc/rendertrust/fe-developer)
Your own site
<a href="https://agentmods.dev/agents/bybren-llc/rendertrust/fe-developer"><img src="https://agentmods.dev/badge/agents/bybren-llc/rendertrust/fe-developer.svg" alt="Measured on agentmods" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,490 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00011 $0.01490
Opus 5 $0.00005 $0.00745
Sonnet 5 $0.00002 $0.00298
Haiku 4.5 $0.00001 $0.00149

Measured yesterday against content hash 065bb6d9282b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

fe-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.

.claude/agents/fe-developer.md · 238 lines

How it starts

The opening of the file, as written. The whole thing — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Frontend Developer

Role Overview

Implements UI components using patterns from patterns_library/. Focus on execution, not discovery.

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 (UI components, pages, client logic)
  • Atomic commits in SAFe format: feat(ui): 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:

  • frontend-patterns - Clerk auth, shadcn/Radix, Next.js App Router patterns
  • pattern-discovery - Pattern library discovery before implementation
  • safe-workflow - Branch naming, commit format, PR workflow

🚀 Quick Start

Your workflow in 4 steps:

  1. Read speccat specs/REN-XXX-{feature}-spec.md
  2. Find pattern → Check spec for pattern reference, read from patterns_library/ui/
  3. Copy & customize → Follow pattern's customization guide
  4. Validate → Run yarn lint && yarn type-check && yarn build

That's it! BSA already did pattern discovery. You just execute.

Success Validation Command

# Full validation before PR
yarn lint && yarn type-check && yarn build && echo "FE SUCCESS" || echo "FE 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

Read the full file on GitHub · 238 lines

Changes

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.

  1. yesterday First seen · 238 lines · 11 tokens per session scan A 065bb6d9282b

Subscribe to this mod's changes

fe-developer is an agent published in the GitHub repository bybren-llc/rendertrust (7 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 1,490 once invoked, about $0.0001 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-04.

Related

Other agents, from other repositories

react18-class-surgeon

Class component migration specialist for React 16/17 → 18.3.1. Migrates all three unsafe lifecycle methods with correct semantic replacements (not just UNSAFE prefix). Migrates legacy context to createContext, string refs to React.createRef(), findDOMNode to direct refs, and ReactDOM.render to createRoot. Uses memory…

github/awesome-copilot · 81 tokens

frontend-dev

Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.

vibeeval/vibecosystem · 22 tokens

react-portfolio-engineer

React portfolio/gallery sites for creatives: React 18+, Next.js App Router, image optimization.

notque/vexjoy-agent · 25 tokens

alchemist

Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…

drobins25/craft · 355 tokens

pywry-builder

Builds PyWry widgets, dashboards, chat UIs, and TradingView charts end‑to‑end by orchestrating the PyWry MCP tools. Use when the user asks to build, scaffold, or iterate on a PyWry app and the work involves multiple MCP tool calls (e.g. create widget → populate data → add toolbar → wire events → export).

deeleeramone/PyWry · 81 tokens

nextjs-expert

Next.js framework strategist. Makes decisions about rendering strategies (SSR/SSG/ISR), App Router patterns, data fetching, and performance optimization. Use when designing Next.js applications, choosing rendering methods, or architecting full-stack React apps.

armanzeroeight/fastagent-plugins · 53 tokens