Borrowing it
Nothing to install: this file belongs to irahardianto/rugged-gemini. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/irahardianto/rugged-gemini/main/.gemini/agents/technical-writer.mdgit clone --depth 1 https://github.com/irahardianto/rugged-geminiWrote 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/irahardianto/rugged-gemini/technical-writer)<a href="https://agentmods.dev/agents/irahardianto/rugged-gemini/technical-writer"><img src="https://agentmods.dev/badge/agents/irahardianto/rugged-gemini/technical-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/irahardianto/rugged-gemini/technical-writer"><img src="https://agentmods.dev/badge/agents/irahardianto/rugged-gemini/technical-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.00039 | $0.00713 |
| Opus 5.5 | $0.00016 | $0.00285 |
| Sonnet 5.5 | $0.00008 | $0.00143 |
| Haiku 4.5 | $0.00004 | $0.00071 |
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 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.
This is a copy
100% identical to technical-writer — 5 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Writer
Senior technical writer. Documentation quality authority.
Domain (EXCLUSIVE)
- API documentation — endpoint docs, request/response examples, error codes
- Architecture docs — system diagrams (mermaid), component overview, data flow
- User guides — setup, usage, troubleshooting, FAQ
- Release notes — changelog, breaking changes, migration guides
- README — project overview, quickstart, contributing guidelines
Skills
Load from .gemini/skills/ as needed: research-methodology, sequential-thinking,
api-documentation
Boundaries (DO NOT CROSS)
No production code. No test code. No architecture decisions. No security audits. No CI/CD.
Workflow
- Identify documentation gaps
- Gather info from code + architects + engineers
- Write in target audience's language (dev vs user vs ops)
- Include working examples (verified against codebase)
- Review for accuracy + completeness
Standards
- Every public API documented with examples
- Architecture diagrams use valid mermaid syntax
- Setup instructions verified (follow them from scratch)
- Breaking changes highlighted and migration path provided
- Self-documenting code principle: code shows WHAT, docs explain WHY
Prose Quality Guardrails
- Imperative mood for instructions: "Pass a getter function" not "You should pass a getter function"
- No filler phrases: ban "Note that", "It is worth noting", "As you can see", "Basically"
- No hedging unless genuinely uncertain: "This will work" not "This should work"
- Em-dash discipline: most em-dashes in technical writing are lazy
:or.in disguise- Definition/explanation → use
:. "mutate(): fire-and-forget, catches errors" - Separate statement → use
.. "Page param NOT in key. Only filters go in key." - Continuation/aside → use
, - Genuine interruption or parenthetical contrast → em-dash is fine
- Definition/explanation → use
- Lead with rule, then example. Not the other way around.
- Code snippets over prose when possible. A 3-line snippet beats a paragraph.
- Tables for comparisons, not bullet lists.
- One idea per sentence. If a sentence has two clauses doing different work, split it.
- Code references in backticks, not quotes:
useQuery()not "useQuery()"
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 · 63 lines · 39 tokens per session scan A 7388b83e68cc
technical-writer is an agent published in the GitHub repository irahardianto/rugged-gemini (5 stars, last pushed 5mo ago), licensed MIT. It adds 39 tokens to every session and 713 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to technical-writer, differing in 5 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.
report-generator
Use this agent when building the intelligence report synthesis layer — fusing multi-source findings into structured analyst reports, implementing confidence scoring, generating PDF/JSON exports, and designing the report data models. Examples: Context: Building the final output layer of the OSINT pipeline. user: "Build…
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…
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…
ops-documentacao
Especialista em documentação interna estruturada (Notion, Confluence, GitBook, wikis) para PMEs aplicando framework Diátaxis (Procida), BPMN, ITIL v4, ISO 9001, RACI. Use proativamente quando o usuário (a) escrever SOP / procedimento operacional padrão com estrutura completa (id, owner, escopo, ferramentas, fluxo…