documentation-sync

documentation-sync is a cursor rule for Cursor from 567-labs/instructor. It costs 249 tokens per session, scanned A, original, MIT.

A documentation checklist for projects that use MkDocs and API reference pages.

In plain words
What is it for?
Use it when changing code, adding documentation or Markdown files, updating APIs, or reviewing documentation quality.
Why use it?
It helps keep documentation, examples, type hints, docstrings, navigation, and installation instructions aligned with code changes.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when changing code, adding documentation or Markdown files, updating APIs, or reviewing documentation quality.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/567-labs/instructor/documentation-sync
About the project

Instructor is a library that helps applications obtain structured, validated data from language models using Pydantic models. It is for developers building LLM features such as data extraction across different model providers, and the catalogue entries add usage rules and instructions.

567-labs/instructor · 14,028 stars · on GitHub · python.useinstructor.com

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/567-labs/instructor

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-sync

README.md
[![agentmods](https://agentmods.dev/badge/rules/567-labs/instructor/documentation-sync/github.svg)](https://agentmods.dev/rules/567-labs/instructor/documentation-sync)
Your own site
<a href="https://agentmods.dev/rules/567-labs/instructor/documentation-sync"><img src="https://agentmods.dev/badge/rules/567-labs/instructor/documentation-sync/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-sync

Your own site · 80×15
<a href="https://agentmods.dev/rules/567-labs/instructor/documentation-sync"><img src="https://agentmods.dev/badge/rules/567-labs/instructor/documentation-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 249 This file is loaded in full into every session.
When invoked 249 The same file — it is already loaded in full.
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.00249 $0.00249
Opus 5.5 $0.00100 $0.00100
Sonnet 5.5 $0.00050 $0.00050
Haiku 4.5 $0.00025 $0.00025

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

Security

Grade A, and why

documentation-sync 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/documentation-sync.mdc · 36 lines

What it actually says

  • When making code changes:

    • Update related documentation files to reflect the changes
    • Check docstrings and type hints are up to date
    • Update any example code in markdown files
    • Review README.md if the changes affect installation or usage
  • When creating new markdown files:

    • Add the file to mkdocs.yml under the appropriate section
    • Follow the existing hierarchy and indentation
    • Use descriptive nav titles
    • Example:
      nav:
        - Home: index.md
        - Guides:
            - Getting Started: guides/getting-started.md
            - Your New File: guides/your-new-file.md
      
  • For API documentation:

    • Ensure new functions/classes are documented
    • Include type hints and docstrings
    • Add usage examples
    • Update API reference docs if auto-generated
  • Documentation Quality:

    • Write at grade 10 reading level (see simple-language.mdc)
    • Include working code examples
    • Add links to related documentation
    • Use consistent formatting and style
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 · 36 lines · 249 tokens per session scan A dc7fc3a9e995

Subscribe to this mod's changes

documentation-sync is a cursor rule published in the GitHub repository 567-labs/instructor (14,028 stars, last pushed 3d ago), licensed MIT. It adds 249 tokens to every session, about $0.0010 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.