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/a-safe-pulseWrote 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/a-safe-pulse/tech-writer)<a href="https://agentmods.dev/agents/bybren-llc/a-safe-pulse/tech-writer"><img src="https://agentmods.dev/badge/agents/bybren-llc/a-safe-pulse/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/a-safe-pulse/tech-writer"><img src="https://agentmods.dev/badge/agents/bybren-llc/a-safe-pulse/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.01280 |
| Opus 5 | $0.00006 | $0.00640 |
| Sonnet 5 | $0.00002 | $0.00256 |
| Haiku 4.5 | $0.00001 | $0.00128 |
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 4d 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.
This is a copy
84% identical to tech-writer — 22 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 — 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 (ASP-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/ASP-XXX-{feature}-spec.md - Find pattern → Check spec for documentation pattern reference
- Copy & customize → Follow pattern's documentation template
- Validate → Run
npx tsc --noEmit:md && npx tsc --noEmit
That's it! BSA defined the documentation strategy. You just execute.
Success Validation Command
# Validate documentation quality
npx tsc --noEmit:md && npx tsc --noEmit && echo "TW SUCCESS" || echo "TW FAILED"
Pattern Execution Workflow
Step 1: Read Your Spec
# Get your assignment
cat specs/ASP-XXX-{feature}-spec.md
# Find the documentation pattern (BSA included this)
grep -A 3 "Pattern:" specs/ASP-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.
- 4d ago First seen · 255 lines · 12 tokens per session scan A 77b87dfb8c36
tech-writer is an agent published in the GitHub repository bybren-llc/a-safe-pulse (9 stars, last pushed 5mo ago), licensed MIT. It adds 12 tokens to every session and 1,280 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to tech-writer, differing in 22 lines, and is treated as a copy.
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.
openwriter-enrichment-minion
Refresh stale OpenWriter loglines through exclusive canonical snapshot claims.
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.
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…
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.
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…