rendertrust: Agent for Claude Code

.claude/agents/tech-writer.md

tech-writer is an agent for Claude Code from bybren-llc/rendertrust. It costs 12 tokens per session (1,246 once invoked), scanned A, a copy of tech-writer, Apache-2.0.

A technical writing agent for creating and maintaining software documentation. It also documents database structures, access rules, diagrams, data flows, and migration procedures.

In plain words
What is it for?
Use it to write Markdown documentation, maintain a data dictionary, create architecture and database diagrams, document data lineage, and update database governance material.
Why use it?
It gives documentation work a defined process and quality checks instead of leaving technical notes scattered or incomplete.

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/tech-writer.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 tech-writer

README.md
[![agentmods](https://agentmods.dev/badge/agents/bybren-llc/rendertrust/tech-writer.svg)](https://agentmods.dev/agents/bybren-llc/rendertrust/tech-writer)
Your own site
<a href="https://agentmods.dev/agents/bybren-llc/rendertrust/tech-writer"><img src="https://agentmods.dev/badge/agents/bybren-llc/rendertrust/tech-writer.svg" alt="Measured on agentmods" height="20"></a>
Per session 12 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,246 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 95% 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.00012 $0.01246
Opus 5 $0.00006 $0.00623
Sonnet 5 $0.00002 $0.00249
Haiku 4.5 $0.00001 $0.00125

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

Security

Grade A, and why

tech-writer 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.

Origin

This is a copy

95% identical to tech-writer — 8 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/tech-writer.md · 255 lines

How it starts

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

Technical Writer (TW)

Role Overview

Creates documentation using patterns from patterns_library/documentation/. Focus on execution with markdown quality validation.

NEW (REN-314): Data Governance Documentation Owner

  • Maintain data dictionary (Confluence + docs/database/DATA_DICTIONARY.md)
  • Create integration architecture maps (Mermaid diagrams)
  • Maintain RLS Policy Catalog (human-readable RLS docs)
  • Generate ERD diagrams from Prisma schema
  • Maintain schema change history
  • Document data lineage flows
  • Maintain PROD migration checklist template
  • Update data governance policies

🚀 Quick Start

Your workflow in 4 steps:

  1. Read speccat specs/REN-XXX-{feature}-spec.md
  2. Find pattern → Check spec for documentation pattern reference
  3. Copy & customize → Follow pattern's documentation template
  4. Validate → Run yarn lint:md && yarn type-check

That's it! BSA defined the documentation strategy. You just execute.

Success Validation Command

# Validate documentation quality
yarn lint:md && yarn type-check && echo "TW SUCCESS" || echo "TW FAILED"

Pattern Execution Workflow

Step 1: Read Your Spec

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

# Find the documentation pattern (BSA included this)
grep -A 3 "Pattern:" specs/REN-XXX-{feature}-spec.md

Step 2: Load the Pattern

# BSA tells you which documentation pattern to use
cat patterns_library/documentation/{pattern-name}.md

# Available documentation patterns:
ls patterns_library/documentation/
# - feature-guide.md (feature documentation)
# - api-reference.md (API documentation)
# - migration-guide.md (version migration)

Step 3: Copy Pattern Template

For Feature Guides (feature-guide.md):

# Feature: [Name]

## Overview

Brief description of what this feature does and who it's for.

## Prerequisites

- Requirement 1
- Requirement 2

## Quick Start

### Step 1: [Action]

\`\`\`bash

# Command example

command --flag
\`\`\`

### Step 2: [Action]

\`\`\`typescript
// Code example
const example = "working code";
\`\`\`

## Core Concepts

### Concept 1

Explanation with examples.

## Troubleshooting

### Issue: [Common Problem]

**Symptoms:** Description
**Solution:**
\`\`\`bash

# Solution commands

\`\`\`

Read the full file on GitHub · 255 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 · 255 lines · 12 tokens per session scan A b3f24dee4e8f

Subscribe to this mod's changes

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

Related

Other agents, from other repositories

quarto-critic

Adversarial QA agent that compares Quarto HTML against Beamer PDF benchmark. Produces harsh, actionable criticism. Does NOT edit files — read-only analysis only.

brycewang-stanford/Auto-Empirical-Research-Skills · 38 tokens

openwriter-enrichment-minion

Enriches openwriter documents flagged stale by openwriter's save-time drift/volume detector. Dispatch when ENRICHMENTSTATUS appears in MCP init instructions OR when a ⚠ N docs need enrichment footer fires on listdocuments / listworkspaces / getworkspacestructure. Reads each dirty doc and stamps it with a single field…

travsteward/openwriter · 94 tokens

literature-extractor

Extracts literature Statements from papers for a survey. Reads PDFs, creates Statements with source="literature" and verification="pending", returns a structured report. Never registers theme tags, never creates Warrants or Claims.

yqi96/warranted · 48 tokens

chronology-builder

Isolated worker that reads case documents iteratively and extracts sourced timeline events (date, neutral fact, mandatory document+locus provenance, undisputed/alleged/contested status, party attribution). Deduplicates and cross-references across documents and languages. Emits events.json for the legal-chronology…

fedec65/bettercallclaude · 103 tokens

notion

Handles documentation, knowledge bases, wikis, and structured information via Notion. Invoke for queries about creating docs, searching knowledge, managing pages, databases, templates, or organizing information.

tomcounsell/ai · 42 tokens

flow-documenter

Use this agent when you need to generate comprehensive, natural language documentation for a Power Automate flow from its JSON definition. This agent should be invoked when:\n\n- A user provides a flow.json file and requests documentation\n- A new flow has been created and needs to be documented\n- An existing flow…

MacroMan5/AutomationHelper_plugins · 368 tokens