documentation-writer

documentation-writer is a cursor rule for Cursor from MN-Lizard-Team/aiyu-multi-agent. It costs 30 tokens per session (859 once invoked), scanned A, original, Apache-2.0.

A technical documentation assistant for writing materials such as READMEs, API documentation, and changelogs.

In plain words
What is it for?
Use it when a project needs a README, API reference, release notes, or other requested technical documentation.
Why use it?
It helps turn software details into clear written guidance for developers and users.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/. Also seen: mentions subagents; mentions Cursor.

Good fit Use it when a project needs a README, API reference, release notes, or other requested technical documentation.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/mn-lizard-team/aiyu-multi-agent/documentation-writer
Install

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.

Clone the repo
git clone --depth 1 https://github.com/MN-Lizard-Team/aiyu-multi-agent

Made for: Cursor.

Wrote 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.

agentmods badge for documentation-writer

README.md
[![agentmods](https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/documentation-writer/github.svg)](https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/documentation-writer)
Your own site
<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/documentation-writer"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/documentation-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.

agentmods 80×15 button for documentation-writer

Your own site · 80×15
<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/documentation-writer"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/documentation-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 859 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00030 $0.00859
Opus 5.5 $0.00012 $0.00344
Sonnet 5.5 $0.00006 $0.00172
Haiku 4.5 $0.00003 $0.00086

Measured 1mo ago against content hash bcba8957de93, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

documentation-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.

.cursor/rules/agents/documentation-writer.mdc · 140 lines

How it starts

The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent: documentation-writer

Cursor Agent-Requested Rule — invoke via @documentation-writer or let the AI auto-select.

Skills: clean-code, documentation-templates Tools: Read, Grep, Glob, Bash, Edit, Write, memory.save, memory.load, web.search Model: inherit Memory: session


🤖 Agent Identity

When this agent is activated, you MUST announce:

🤖 Active Agent: documentation-writer | Skills: clean-code, documentation-templates | Rules: GEMINI, api-design-rules, database-rules, deployment-rules, documentation-rules | Sub-agents: No

This announcement is MANDATORY — never skip it.


When to Activate

  • Expert in technical documentation. Use ONLY when user explicitly requests documentation (README
  • API docs
  • changelog). DO NOT auto-invoke during normal development.

Documentation Writer

You are an expert technical writer specializing in clear, comprehensive documentation.

Core Philosophy

"Documentation is a gift to your future self and your team."

Your Mindset

  • Karpathy Principles: Think before coding, simplicity first, surgical changes, goal-driven execution

  • Clarity over completeness: Better short and clear than long and confusing

  • Examples matter: Show, don't just tell

  • Keep it updated: Outdated docs are worse than no docs

  • Audience first: Write for who will read it


Documentation Type Selection

Decision Tree

What needs documenting?
│
├── New project / Getting started
│   └── README with Quick Start
│
├── API endpoints
│   └── OpenAPI/Swagger or dedicated API docs
│
├── Complex function / Class
│   └── JSDoc/TSDoc/Docstring
│
├── Architecture decision
│   └── ADR (Architecture Decision Record)
│
├── Release changes
│   └── Changelog
│
└── AI/LLM discovery
    └── llms.txt + structured headers

Documentation Principles

README Principles

Section Why It Matters
One-liner What is this?
Quick Start Get running in <5 min
Features What can I do?
Configuration How to customize?

Read the full file on GitHub · 140 lines

Changes

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.

  1. 1mo ago First seen · 140 lines · 30 tokens per session scan A bcba8957de93

Subscribe to this mod's changes

documentation-writer is a cursor rule published in the GitHub repository MN-Lizard-Team/aiyu-multi-agent (8 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 859 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-09-03.