docs

docs is a cursor rule for Cursor from gabrielmoreira/agent-skills-mirror. It costs 0 tokens per session (684 once invoked), scanned A, a copy of docs, MIT.

A set of rules for maintaining the project’s documentation directory. It defines the documentation structure, Markdown format, headings, and locations for topics such as setup, architecture, storage, and internationalization.

In plain words
What is it for?
Use it when adding, reorganizing, or reviewing Markdown files in `/docs`, including guides, architecture notes, roadmap pages, and error-handling documentation.
Why use it?
It prevents new or edited documentation from being placed inconsistently or using different formatting conventions.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when adding, reorganizing, or reviewing Markdown files in /docs, including guides, architecture notes, roadmap pages, and error-handling documentation.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/gabrielmoreira/agent-skills-mirror/docs
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/gabrielmoreira/agent-skills-mirror

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 docs

README.md
[![agentmods](https://agentmods.dev/badge/rules/gabrielmoreira/agent-skills-mirror/docs/github.svg)](https://agentmods.dev/rules/gabrielmoreira/agent-skills-mirror/docs)
Your own site
<a href="https://agentmods.dev/rules/gabrielmoreira/agent-skills-mirror/docs"><img src="https://agentmods.dev/badge/rules/gabrielmoreira/agent-skills-mirror/docs/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 docs

Your own site · 80×15
<a href="https://agentmods.dev/rules/gabrielmoreira/agent-skills-mirror/docs"><img src="https://agentmods.dev/badge/rules/gabrielmoreira/agent-skills-mirror/docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 684 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 100% copy Near-identical to another mod 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.00000 $0.00684
Opus 5.5 $0.00000 $0.00274
Sonnet 5.5 $0.00000 $0.00137
Haiku 4.5 $0.00000 $0.00068

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

Security

Grade A, and why

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

Origin

This is a copy

100% identical to docs — 0 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.

mirrors/repos/AgentDock@AgentDock/.cursor/rules/docs.mdc · 63 lines

How it starts

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

Documentation Rules (/docs)

This file provides guidelines for working with the documentation in the /docs directory.

Documentation Structure

The /docs directory is organized as follows:

  • [docs/README.md](mdc:docs/README.md): Main project overview
  • [docs/getting-started.md](mdc:docs/getting-started.md): Setup instructions
  • [docs/architecture/](mdc:docs/architecture): System design documentation
  • [docs/nodes/](mdc:docs/nodes): Node system documentation
  • [docs/oss-client/](mdc:docs/oss-client): Client application docs
  • [docs/rfa/](mdc:docs/rfa): "Requests for Architecture" (RFA) process
  • [docs/roadmap/](mdc:docs/roadmap): Future development plans
  • [docs/roadmap.md](mdc:docs/roadmap.md): High-level roadmap
  • [docs/agent-templates.md](mdc:docs/agent-templates.md): Agent template structure
  • [docs/i18n/](mdc:docs/i18n): Internationalization documentation
  • [docs/error-handling/](mdc:docs/error-handling): Error handling guidelines
  • [docs/storage/](mdc:docs/storage): Storage systems documentation
  • Additional files for specific topics

Documentation Standards

  • Markdown Format: Use GitHub Flavored Markdown
  • Headers: Use ATX-style headers (# H1, ## H2) with proper hierarchy
  • Code Examples: Use fenced code blocks with language specifiers
    // TypeScript example
    function example(): string {
      return \"Hello World\";
    }
    
  • Links: Use relative links to other docs in the repository
  • Images: Store in an assets or images directory next to the relevant docs
  • Diagrams: Prefer Mermaid diagrams for technical illustrations
  • Tables: Use standard Markdown tables for tabular data
  • Centralized Location: All user-facing documentation (guides, architecture overviews, API docs, etc.) must be placed in the main /docs directory at the root of the repository. Do not place documentation within the /agentdock-core directory, as the core is not published as a standalone package yet and all documentation is hosted centrally.

Read the full file on GitHub · 63 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 · 63 lines · 0 tokens per session scan A 2b8995d7ea5a

Subscribe to this mod's changes

docs is a cursor rule published in the GitHub repository gabrielmoreira/agent-skills-mirror (19 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 684 tokens. A static security scan graded it A with 0 findings. It is 100% identical to docs, differing in 0 lines, and is treated as a copy.