Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/bybren-llc/safe-agentic-workflowWrote 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/safe-agentic-workflow/tech-writer)<a href="https://agentmods.dev/agents/bybren-llc/safe-agentic-workflow/tech-writer"><img src="https://agentmods.dev/badge/agents/bybren-llc/safe-agentic-workflow/tech-writer/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.
<a href="https://agentmods.dev/agents/bybren-llc/safe-agentic-workflow/tech-writer"><img src="https://agentmods.dev/badge/agents/bybren-llc/safe-agentic-workflow/tech-writer.svg" alt="Reviewed on agentmods" width="80" 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.00012 | $0.01259 |
| Opus 5.5 | $0.00005 | $0.00504 |
| Sonnet 5.5 | $0.00002 | $0.00252 |
| Haiku 4.5 | $0.00001 | $0.00126 |
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 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- tech-writer — 95% identical, 8 lines differ
- tech-writer — 84% identical, 22 lines differ
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 ({{TICKET_PREFIX}}-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:
- Read spec →
cat specs/{{TICKET_PREFIX}}-XXX-{feature}-spec.md - Find pattern → Check spec for documentation pattern reference
- Copy & customize → Follow pattern's documentation template
- 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/{{TICKET_PREFIX}}-XXX-{feature}-spec.md
# Find the documentation pattern (BSA included this)
grep -A 3 "Pattern:" specs/{{TICKET_PREFIX}}-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
\`\`\`
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.
- 1mo ago First seen · 255 lines · 12 tokens per session scan A abe2659f19c3
tech-writer is an agent published in the GitHub repository bybren-llc/safe-agentic-workflow (425 stars, last pushed 3mo ago), licensed MIT. It adds 12 tokens to every session and 1,259 once invoked, about $0.0000 per session on Opus 5.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-08-30.
Other agents, from other repositories
technical-director
High-level technical decisions — engine architecture, technology choices, performance strategy, technical risk, cross-system conflicts.
ai-programmer
Implements game AI — behavior trees, state machines, pathfinding, perception, decision-making, NPC and enemy behavior, AI debugging.
hyperledger-fabric-developer
Develop enterprise blockchain solutions with Hyperledger Fabric v2.5 LTS and v3.x. Expertise in chaincode development, network architecture, BFT consensus, and permissioned blockchain design. Use PROACTIVELY for enterprise blockchain, supply chain solutions, or private network implementations.
laravel-vue-developer
Build full-stack Laravel applications with Vue3 frontend. Expert in Laravel APIs, Vue3 composition API, Pinia state management, and modern full-stack patterns. Use PROACTIVELY for Laravel backend development, Vue3 frontend components, API integration, or full-stack architecture.
legal-advisor
Draft privacy policies, terms of service, disclaimers, and legal notices. Creates GDPR-compliant texts, cookie policies, and data processing agreements. Use PROACTIVELY for legal documentation, compliance texts, or regulatory requirements.
data-scientist
Data analysis expert for SQL queries, BigQuery operations, and data insights. Use proactively for data analysis tasks and queries.