rendertrust: Agent for Claude Code

.claude/agents/security-engineer.md

security-engineer is an agent for Claude Code from bybren-llc/rendertrust. It costs 16 tokens per session (1,531 once invoked), scanned A, a copy of security-engineer, Apache-2.0.

A security engineer agent for checking row-level security, data-access rules, vulnerability scans, and compliance procedures such as data retention and deletion.

In plain words
What is it for?
Use it to audit database access, validate policies for new tables, run security checks, review production migration plans, and check GDPR-related procedures.
Why use it?
It gives security validation a defined owner instead of relying on feature developers to assess access isolation and production migration risks themselves.

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/security-engineer.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 security-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/bybren-llc/rendertrust/security-engineer/github.svg)](https://agentmods.dev/agents/bybren-llc/rendertrust/security-engineer)
Your own site
<a href="https://agentmods.dev/agents/bybren-llc/rendertrust/security-engineer"><img src="https://agentmods.dev/badge/agents/bybren-llc/rendertrust/security-engineer/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for security-engineer

Your own site · 80×15
<a href="https://agentmods.dev/agents/bybren-llc/rendertrust/security-engineer"><img src="https://agentmods.dev/badge/agents/bybren-llc/rendertrust/security-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 16 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,531 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 91% copy Near-identical to another mod 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.00016 $0.01531
Opus 5.5 $0.00006 $0.00612
Sonnet 5.5 $0.00003 $0.00306
Haiku 4.5 $0.00002 $0.00153

Measured 1mo ago against content hash e454cb9506f6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

security-engineer 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 1mo ago.

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.

Origin

This is a copy

91% identical to security-engineer — 16 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.

.claude/agents/security-engineer.md · 247 lines

How it starts

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

Security Engineer (SecEng)

Role Overview

Validates security implementation using patterns from patterns_library/security/. Focus on RLS enforcement, vulnerability scanning, and security audits.

NEW (REN-314): RLS & Compliance Owner

  • Validate RLS policies for new tables (see ../../docs/database/RLS_POLICY_CATALOG.md)
  • Audit data access patterns (user isolation verification)
  • Validate GDPR/compliance procedures (data retention, deletion, export)
  • Review data retention policies (see DATA_GOVERNANCE_POLICY.md)
  • Security review of PROD migration plans (MANDATORY before execution)

🚀 Quick Start

Your workflow in 4 steps:

  1. Read spec → cat specs/REN-XXX-{feature}-spec.md
  2. Find pattern → Check spec for security pattern reference
  3. Copy & validate → Follow pattern's security validation guide
  4. Audit → Run npm audit && yarn lint && RLS validation

That's it! BSA defined the security requirements. You just validate.

Success Validation Command

# Full security validation
cat scripts/rls-phase4-final-validation.sql | docker exec -i rendertrust-postgres-1 psql -U {{PROJECT}}_app_user -d {{PROJECT}}_dev && npm audit --audit-level=high && yarn lint && echo "SECURITY SUCCESS" || echo "SECURITY FAILED"

Pattern Execution Workflow

Step 1: Read Your Spec

# Get your assignment
cat specs/REN-XXX-{feature}-spec.md

# Find the security requirements (BSA included this)
grep -A 5 "Security:" specs/REN-XXX-{feature}-spec.md

Step 2: Load the Security Pattern

# BSA tells you which security validation to run
cat patterns_library/security/{pattern-name}.md

# Available security patterns:
ls patterns_library/security/
# - rls-validation.md (RLS enforcement check)
# - api-security-audit.md (API security review)
# - vulnerability-scan.md (dependency audit)

Step 3: Execute Security Validation

For RLS Validation (rls-validation.md):

# Automated RLS check
cat scripts/rls-phase4-final-validation.sql | docker exec -i rendertrust-postgres-1 psql -U {{PROJECT}}_app_user -d {{PROJECT}}_dev

# Expected output:
# ✓ User isolation enforced
# ✓ Admin access controlled
# ✓ System context functional

Read the full file on GitHub · 247 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. 1mo ago First seen · 247 lines · 16 tokens per session scan A e454cb9506f6

Subscribe to this mod's changes

security-engineer is an agent published in the GitHub repository bybren-llc/rendertrust (7 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 1,531 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to security-engineer, differing in 16 lines, and is treated as a copy.

Related

Other agents, from other repositories

MS-SQL Database Administrator

Work with Microsoft SQL Server databases using the MS SQL extension.

github/awesome-copilot · 18 tokens

core-data-auditor

Use this agent when the user mentions Core Data review, schema migration, production crashes, or data safety checking.

CharlesWiltgen/Axiom · 28 tokens

lens

Turns raw data into actionable decisions — dashboards, metric definitions, SQL analytics, funnel and cohort analysis across BI platforms. Use when designing a dashboard, defining KPIs, or running funnel analysis. Trigger with "design a dashboard", "analyze our funnel".

jeremylongshore/tons-of-skills-marketplace · 53 tokens

ecto-schema-designer

Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.

oliver-kriska/claude-elixir-phoenix · 30 tokens

django-migrations-specialist

Database specialist for Django, runs in the "database" extra phase after development. Finalizes model field types and Meta indexes/constraints, runs makemigrations, reviews generated SQL with sqlmigrate, runs migrate, verifies with migrate --check. Do NOT use for: application logic (django-architect), tests…

AratKruglik/claude-sdlc · 85 tokens

database-architect

Use this agent for database design and change work: schema design, indexing strategy, query optimization, migration safety, and engine selection. Trigger on "design a schema for", "this query is slow", "is this migration safe", "add an index", "Postgres or Mongo for this", or N+1 complaints. Returns schema/DDL with…

aayushostwal/nexus · 96 tokens