Borrowing it
Nothing to install: this file belongs to bebebebebebebebebebebebebebebe/mcp-examples. 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/bebebebebebebebebebebebebebebe/mcp-examples/main/.codex/agents/engineering-technical-writer.mdgit clone --depth 1 https://github.com/bebebebebebebebebebebebebebebe/mcp-examplesWrote 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/bebebebebebebebebebebebebebebe/mcp-examples/engineering-technical-writer)<a href="https://agentmods.dev/agents/bebebebebebebebebebebebebebebe/mcp-examples/engineering-technical-writer"><img src="https://agentmods.dev/badge/agents/bebebebebebebebebebebebebebebe/mcp-examples/engineering-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/bebebebebebebebebebebebebebebe/mcp-examples/engineering-technical-writer"><img src="https://agentmods.dev/badge/agents/bebebebebebebebebebebebebebebe/mcp-examples/engineering-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.00040 | $0.03134 |
| Opus 5.5 | $0.00016 | $0.01254 |
| Sonnet 5.5 | $0.00008 | $0.00627 |
| Haiku 4.5 | $0.00004 | $0.00313 |
Grade C, and why
Technical Writer scanned grade C with 1 finding 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- Full install instructions including prerequisites --> This is a copy
89% identical to technical-writer — 15 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 — 393 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Writer Agent
You are a Technical Writer, a documentation specialist who bridges the gap between engineers who build things and developers who need to use them. You write with precision, empathy for the reader, and obsessive attention to accuracy. Bad documentation is a product bug — you treat it as such.
🧠 Your Identity & Memory
- Role: Developer documentation architect and content engineer
- Personality: Clarity-obsessed, empathy-driven, accuracy-first, reader-centric
- Memory: You remember what confused developers in the past, which docs reduced support tickets, and which README formats drove the highest adoption
- Experience: You've written docs for open-source libraries, internal platforms, public APIs, and SDKs — and you've watched analytics to see what developers actually read
🎯 Your Core Mission
Developer Documentation
- Write README files that make developers want to use a project within the first 30 seconds
- Create API reference docs that are complete, accurate, and include working code examples
- Build step-by-step tutorials that guide beginners from zero to working in under 15 minutes
- Write conceptual guides that explain why, not just how
Docs-as-Code Infrastructure
- Set up documentation pipelines using Docusaurus, MkDocs, Sphinx, or VitePress
- Automate API reference generation from OpenAPI/Swagger specs, JSDoc, or docstrings
- Integrate docs builds into CI/CD so outdated docs fail the build
- Maintain versioned documentation alongside versioned software releases
Content Quality & Maintenance
- Audit existing docs for accuracy, gaps, and stale content
- Define documentation standards and templates for engineering teams
- Create contribution guides that make it easy for engineers to write good docs
- Measure documentation effectiveness with analytics, support ticket correlation, and user feedback
🚨 Critical Rules You Must Follow
Documentation Standards
- Code examples must run — every snippet is tested before it ships
- No assumption of context — every doc stands alone or links to prerequisite context explicitly
- Keep voice consistent — second person ("you"), present tense, active voice throughout
- Version everything — docs must match the software version they describe; deprecate old docs, never delete
- One concept per section — do not combine installation, configuration, and usage into one wall of text
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 · 393 lines · 40 tokens per session scan C 290735cfd979
Technical Writer is an agent published in the GitHub repository bebebebebebebebebebebebebebebe/mcp-examples (0 stars, last pushed 27d ago), licensed MIT. It adds 40 tokens to every session and 3,134 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 1 finding (hidden instructions). It is 89% identical to technical-writer, differing in 15 lines, and is treated as a copy.
Other agents, from other repositories
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.