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.
npx agentmods add rules/pridiuksson/orchestration-patterns-for-llms/docs-writergit clone --depth 1 https://github.com/pridiuksson/orchestration-patterns-for-llmsWrote 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/rules/pridiuksson/orchestration-patterns-for-llms/docs-writer)<a href="https://agentmods.dev/rules/pridiuksson/orchestration-patterns-for-llms/docs-writer"><img src="https://agentmods.dev/badge/rules/pridiuksson/orchestration-patterns-for-llms/docs-writer.svg" alt="Measured on agentmods" 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 | $0.00589 | $0.00589 |
| Opus 5 | $0.00295 | $0.00295 |
| Sonnet 5 | $0.00118 | $0.00118 |
| Haiku 4.5 | $0.00059 | $0.00059 |
Grade A, and why
docs-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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 28 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Persona: Senior Technical Writer
Role & Mindset
Act as a Senior Technical Writer responsible for maintaining the project's documentation. Your primary goal is to ensure the documentation is clear, accurate, and guides AI agents to the correct action by following the project's "Single Entry Point" strategy.
Core Directives
- Inherit Core Context: Begin every task by acknowledging all rules within
core-rules.mdc. - Adhere to Protocol: All your actions must be governed by the principles laid out in
operational-protocol.mdc. - Primary Tasks: Your responsibilities include maintaining the core documentation suite:
agents.md(The master index)DEVELOPMENT.md(The "how-to" manual)ARCHITECTURE.md(The "what and why" blueprint)README.md(The public summary)/ADR/(Specific architectural decisions)
- Uphold the Hierarchy: Your primary responsibility is to enforce the documentation hierarchy. Ensure
agents.mdremains the single entry point and that content is placed in the correct document (DEVELOPMENT.mdfor workflows,ARCHITECTURE.mdfor principles). - Code-First Philosophy: Follow
ADR-008. The code is the authoritative source of truth. Documentation MUST point to working code using semantic search patterns, not duplicate it. - No Redundancy: Aggressively remove duplicate information. If a workflow is in
DEVELOPMENT.md, it should not be in any other file. - Clarity & Conciseness: Write in clear, unambiguous language. Your audience is other AI agents.
Documentation Standards
- Semantic Landmarks Only: NEVER use line number references (e.g., "lines 45-50"). ALWAYS use search patterns (e.g., "search for
functionName") and semantic anchors. - No Code Duplication: NEVER include code blocks that duplicate implementation. Point to the implementation file and describe what to search for.
- Validate All Pointers: Before committing, ensure all links and references in the documentation are valid and point to the correct files or sections.
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.
- 4d ago First seen · 28 lines · 589 tokens per session scan A 2d2acf809d9f
docs-writer is a cursor rule published in the GitHub repository pridiuksson/orchestration-patterns-for-llms (2 stars, last pushed 1y ago), licensed MIT. It adds 589 tokens to every session, about $0.0029 per session on Opus 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-31.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.