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/timurgaleev/vibestackWrote 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/timurgaleev/vibestack/technical-writer)<a href="https://agentmods.dev/agents/timurgaleev/vibestack/technical-writer"><img src="https://agentmods.dev/badge/agents/timurgaleev/vibestack/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/timurgaleev/vibestack/technical-writer"><img src="https://agentmods.dev/badge/agents/timurgaleev/vibestack/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.00047 | $0.03175 |
| Opus 5.5 | $0.00019 | $0.01270 |
| Sonnet 5.5 | $0.00009 | $0.00635 |
| Haiku 4.5 | $0.00005 | $0.00317 |
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 19d 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 --> Copies of this mod
3 near-identical copies found in the catalogue:
- technical-writer — 92% identical, 15 lines differ
- Technical Writer — 89% identical, 14 lines differ
- Technical Writer — 89% identical, 15 lines differ
How it starts
The opening of the file, as written. The whole thing — 398 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.
- 19d ago First seen · 398 lines · 47 tokens per session scan C fc6725e31307
technical-writer is an agent published in the GitHub repository timurgaleev/vibestack (7 stars, last pushed 7d ago), licensed MIT. It adds 47 tokens to every session and 3,175 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-19.
Other agents, from other repositories
doc-formatter
A document-formatting agent that turns supplied content into a new HTML document, using a built-in layout or the style of a reference document. HTML is the format used to structure pages for web browsers.
docs-ux-audit-agent
Reader-experience auditor for one docs shard. Reads every page in full, scores the rubric, and returns evidence-backed findings in ledger format.
docs
Use when code needs documentation - API docs, architecture diagrams, user guides, ADRs, JSDoc/TSDoc comments, or onboarding materials.
database-architect
Use when you need to design database schemas, plan migrations, model data relationships, choose between SQL and NoSQL, or architect data layers for scalability and performance.
security-auditor
Use when you need security review of API endpoints, authentication flows, data handling, dependency auditing, or compliance verification against OWASP standards.
tech-writer
Use when creating client-facing documentation, writing API references, building user guides, maintaining the knowledge base, or when any deliverable needs accompanying documentation before it can be shipped to a client.