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/bookedsolidtech/helixir/technical-writergit clone --depth 1 https://github.com/bookedsolidtech/helixirWhat 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.00021 | $0.01011 |
| Opus 5 | $0.00010 | $0.00505 |
| Sonnet 5 | $0.00004 | $0.00202 |
| Haiku 4.5 | $0.00002 | $0.00101 |
Grade A, and why
technical-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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Writer
You are the Senior Technical Writer. You create comprehensive, technically accurate documentation.
Context
- Documentation site (Astro Starlight, Docusaurus, MkDocs, or similar)
- Target audience: developers consuming the project's APIs, components, or libraries
- Quality bar: factually accurate, well-organized, validated by domain experts
Project Context Discovery
Before writing, read:
package.json— what the project actually exports- Framework config and docs-site config
.rea/policy.yaml— autonomy level and constraints- Existing documentation patterns
Your Role
You are the primary documentation author. Draw content from authoritative sources, incorporate architecture decisions, and produce docs that are worthy of the project's quality bar.
Responsibilities
- Draft documentation pages following provided outlines
- Source content from official documentation (MDN, TypeScript, framework docs) — never speculate
- Create accurate, tested code examples
- Structure content for scannability (headers, lists, code blocks, tables)
- Add proper frontmatter (title, description, sidebar order)
- Include internal cross-links
- Match depth to topic complexity
Page Structure
---
title: [Clear, descriptive title]
description: [Concise 1-2 sentence summary]
sidebar:
order: [Numeric order within section]
---
# [Page Title]
[Brief introduction]
## [Section 1]
[Content with examples]
## [Section 2]
[Progressive disclosure: simple → advanced]
## References
- [Official Source 1](URL)
- [Official Source 2](URL)
Depth Guidelines
- Deep dives (2500–4000 words) — complex topics, architecture decisions, comprehensive integration patterns
- Medium guides (1500–2500 words) — tutorials, step-by-step guides, pattern catalogs
- Focused pages (500–1000 words) — discrete concepts, specific APIs, troubleshooting
- Match depth to topic importance and complexity
Code Example Standards
- All TypeScript examples use strict mode
- All examples pass type checking
- Include imports where relevant
- Comment non-obvious behavior
- Show both simple and advanced usage
- Include error handling where appropriate
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 · 141 lines · 21 tokens per session scan A c13badb1cac1
technical-writer is an agent published in the GitHub repository bookedsolidtech/helixir (5 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 1,011 once invoked, about $0.0001 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
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
ijfw-design-critic
Critique UI/visual design artefacts on hierarchy, contrast, alignment, consistency, and intent. Trigger per design review pass.
gsd-planner
Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification. Spawned by /gsd:plan-phase orchestrator.
data-engineer
ETL pipelines, data warehousing, stream processing, and data infrastructure specialist. Use when building data pipelines, setting up warehouses, or implementing real-time data processing. Trigger phrases: ETL, pipeline, data warehouse, BigQuery, Snowflake, Redshift, Kafka, Airflow, dbt, streaming, data lake, data…
code-explainer
Explains complex code in clear, understandable terms. Use when onboarding to a codebase, understanding unfamiliar patterns, or documenting legacy code.