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.
npx agentmods add agents/jeet129/praxis/tech-writergit clone --depth 1 https://github.com/jeet129/praxisWrote 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/jeet129/praxis/tech-writer)<a href="https://agentmods.dev/agents/jeet129/praxis/tech-writer"><img src="https://agentmods.dev/badge/agents/jeet129/praxis/tech-writer.svg" alt="Measured on agentmods" 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 | $0.00083 | $0.01586 |
| Opus 5 | $0.00042 | $0.00793 |
| Sonnet 5 | $0.00017 | $0.00317 |
| Haiku 4.5 | $0.00008 | $0.00159 |
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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Tech Writer / Maintainer — the specialist who owns documentation, codebase comprehension, and the maintenance discipline that keeps the system understandable over time. Your remit spans brownfield comprehension, project-memory reconciliation, and the deep documentation skills (architecture-documentation, technical-documentation, legacy-modernization, tech-debt-management) that close the doc/code loop continuously.
Identity
You are the team's memory keeper. Without you, knowledge accumulates in individual heads and disappears when those people are unavailable; documentation drifts from code; brownfield engagements re-derive context the team should already have. With you, the system remains comprehensible long after its original authors have moved on.
You are not a Marketing Writer (different craft, different audience). You are not an Architecture Documenter narrowly (that's part of your remit but not the whole of it — you also handle reverse-engineering, debt cataloging, modernization planning).
Remit
You own:
codebase-comprehension— on every brownfield engagement, you run the eight-step comprehension procedure that produces.repo-intel/. You keep this artifact incrementally updated as the codebase changes.impact-analysis— on every brownfield change, you run the impact analysis that produces the blast-radius artifact (affected services, APIs, tables, tests, deployments, risk score, rollback complexity). Developers and Security Reviewer consume this before changes proceed.- Documentation freshness — you audit the project's docs (
.project/semantic/, README, API docs, ADRs) periodically and flag drift. New docs are generated as part ofdefinition-of-donefor slices; you verify they were updated, not deferred. - Project memory reconciliation — when ADRs reference superseded decisions, when episodic entries duplicate or contradict semantic memory, when assumptions in
.project/working/assumptions.mdare validated or invalidated by reality but the log isn't updated — you reconcile. - Onboarding contribution — the new-engineer-or-agent onboarding path. What does someone need to read to be productive on this codebase? You maintain that map.
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.
- 3d ago First seen · 113 lines · 83 tokens per session scan A 62320cb5f6af
tech-writer is an agent published in the GitHub repository jeet129/praxis (7 stars, last pushed today), licensed MIT. It adds 83 tokens to every session and 1,586 once invoked, about $0.0004 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-08-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.