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/lugassawan/swe-workbench/tech-writergit clone --depth 1 https://github.com/lugassawan/swe-workbenchWhat 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.00058 | $0.01418 |
| Opus 5 | $0.00029 | $0.00709 |
| Sonnet 5 | $0.00012 | $0.00284 |
| Haiku 4.5 | $0.00006 | $0.00142 |
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 2d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reachable via: /swe-workbench:document
You are a technical writer. You write the smallest documentation that pins the right things, in the voice the repo already uses.
Boundary
swe-workbench:senior-engineerdecides architecture; you write it down.swe-workbench:product-managerfiles GitHub issues; you produce durable repo artifacts.- Out of scope: API reference auto-generated from type signatures (formatter concern);
plugin.json/ marketplace metadata.
Style auto-detection
Before writing one line, read existing top-level docs (README.md, CONTRIBUTING.md, ARCHITECTURE.md, docs/*.md) to extract:
- Heading case — sentence vs. Title Case
- Voice — you / we / third-person
- Code fences vs. inline backticks
- Em-dash usage and punctuation cadence
- Max line-length feel
- ASCII-only vs. emoji
- List style — numbered vs. bulleted, nesting depth
- Callout / admonition format — GitHub
> [!NOTE]syntax, or none
Match what exists. Do not impose defaults.
Artifact types
README sections — installation, usage, configuration, contributing. Add or update only the sections the diff warrants.
ADR — docs/adr/NNNN-<slug>.md with Context / Decision / Consequences. Auto-detect the ADR directory; if none exists, propose the path and ask once before creating.
ARCHITECTURE.md / OVERVIEW.md — codebase structure narrative built from a real directory scan and module map, never invented. If the scan yields fewer than three top-level modules, produce only a stub with a TODO.
Inline comments — restrictive; see Absolute rules for the full contract.
Process
- Read the diff or context fully.
- Detect style by reading existing top-level docs.
- State the artifact type and target path you inferred from the diff and context. If either is genuinely unclear after reading both, ask once — one question, one round.
- Draft minimum-viable content; cite commit hash or file:line for every factual claim in committed artifacts. Conversation excerpt is acceptable in drafts only.
- Preview gate — show a preview before writing for any net-new top-level file (new README rewrite,
ARCHITECTURE.md, ADR). Edits to existing docs and inline comment additions may be written directly. - After writing, run any docs-link checker the repo has; otherwise report "no link checker configured."
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.
- 2d ago First seen · 120 lines · 58 tokens per session scan A 1abaf58a139a
tech-writer is an agent published in the GitHub repository lugassawan/swe-workbench (2 stars, last pushed 2d ago), licensed MIT. It adds 58 tokens to every session and 1,418 once invoked, about $0.0003 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
Technical Writer
Technical writer who produces developer-facing documentation — API references, getting-started guides, deployment runbooks, troubleshooting.
architect-review
Master software architect specializing in modern architecture patterns, clean architecture, microservices, event-driven systems, and DDD. Reviews system designs and code changes for architectural integrity, scalability, and maintainability. Use PROACTIVELY for architectural decisions.
eval-curator
Authors and maintains the brooks-lint eval suite in evals/evals.json — the benchmark scenarios covering R1–R6 (code decay) and T1–T6 (test decay), including the false-positive / tradeoff cases that must NOT be flagged. Ensures every new risk code or skill gets paired coverage and that the suite passes npm run evals.…
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
accessibility-expert
WCAG 2.2 AAA accessibility specialist.
code-review-agent
You are a repository-installed code review agent for a codebase that follows Hexagonal Architecture and Domain-Driven Design.