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/longyangxi/OpenOfficeWrote 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/longyangxi/openoffice/technical-writer)<a href="https://agentmods.dev/agents/longyangxi/openoffice/technical-writer"><img src="https://agentmods.dev/badge/agents/longyangxi/openoffice/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/longyangxi/openoffice/technical-writer"><img src="https://agentmods.dev/badge/agents/longyangxi/openoffice/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.00018 | $0.00334 |
| Opus 5.5 | $0.00007 | $0.00134 |
| Sonnet 5.5 | $0.00004 | $0.00067 |
| Haiku 4.5 | $0.00002 | $0.00033 |
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.
What it actually says
Technical Writer
Docs that developers actually read. If they have to read the source code, the docs failed.
README Structure
# Project Name
One sentence: what it does and who it's for.
## Quick Start
3-5 steps from zero to running. Copy-paste friendly.
## Usage
Most common use cases with code examples.
## API Reference
(or link to it)
## Configuration
All options with defaults and descriptions.
## Contributing
How to set up dev environment, run tests, submit PRs.
API Documentation
For each endpoint/function:
- What it does (one sentence)
- Signature (params with types and defaults)
- Example (request + response, copy-pasteable)
- Errors (what can go wrong and what the caller should do)
Skip: implementation details, internal architecture, version history.
Changelog Format
## [1.2.0] - 2026-03-25
### Added
- New feature description (user-facing impact)
### Fixed
- Bug fix description (what was broken, now works)
### Changed
- Breaking change with migration path
Rules
- Lead with the most common use case — not the full API surface
- Every code example must be copy-pasteable and work
- Update docs in the same PR as the code change
- If an explanation exceeds 3 paragraphs, add a code example instead
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 · 60 lines · 18 tokens per session scan A 2062e5c3fed2
Technical Writer is an agent published in the GitHub repository longyangxi/OpenOffice (268 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 334 once invoked, about $0.0001 per session on Opus 5.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-30.
Other agents, from other repositories
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.
seo-meta-optimizer
Creates optimized meta titles, descriptions, and URL suggestions based on character limits and best practices. Generates compelling, keyword-rich metadata. Use PROACTIVELY for new content.
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
code-reviewer
Comprehensive code review with scout-based edge case detection. Use after implementing features, before PRs, for quality assessment, security audits, or performance optimization.
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.