agentmods.dev

docs-site

Rules for an Astro and Starlight documentation site whose content pages and README are generated from project assets. They describe the commands for generating, building, previewing, and checking the docs.

In plain words
What is it for?
Use them when maintaining the docs site, generating content pages, building or previewing documentation, cleaning generated files, and checking whether the README is current.
Why use it?
They prevent manual edits from being lost and make sure generated documentation is checked through the supported workflow.

Cursor rule for Cursor

5 11d ago A scan 0 tokens original MIT
View the source file wyattowalsh/agents
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.

agentmods
npx agentmods add rules/wyattowalsh/agents/docs-site
Clone the repo
git clone --depth 1 https://github.com/wyattowalsh/agents

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 387 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00387
Opus 5 $0.00000 $0.00193
Sonnet 5 $0.00000 $0.00077
Haiku 4.5 $0.00000 $0.00039

Measured 2d ago against content hash 626921032df1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

docs-site 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 2d 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/docs-site.mdc · 44 lines

What it actually says

Docs Site Rules

The docs site is an Astro + Starlight project. Generated content pages are produced from repo assets; do not edit them by hand.

Generated Content

  • wagents docs generate — Generates MDX content pages from skills, agents, and MCP servers.
  • wagents docs generate --include-installed — Opts in to including installed skills from the normalized harness inventory.
  • wagents docs generate --include-drafts — Includes skills with TODO descriptions.
  • Never hand-edit generated MDX files. They are overwritten on the next generation run.

Workflow Commands

wagents docs init       # One-time: pnpm install in docs/
wagents docs dev        # Generate + launch dev server
wagents docs build      # Generate + static build
wagents docs preview    # Generate + build + preview server
wagents docs clean      # Remove generated content pages

README

  • README.md is fully generated from repo contents via wagents readme.
  • wagents readme --check exits 1 if README.md is stale (use in CI).
  • Do not hand-edit README.md; modify the source assets and regenerate.

CI/CD

  • The release-skills.yml workflow validates assets on every PR.
  • It automatically packages and releases skills when a version tag (v*.*.*) is pushed.
  • Ensure wagents validate and wagents readme --check pass before merging.

Docs Steward

  • After changes to public APIs, file structure, agent definitions, or skill definitions, invoke the docs-steward skill if available to keep documentation in sync.
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. 2d ago First seen · 44 lines · 0 tokens per session scan A 626921032df1

Subscribe to this mod's changes

docs-site is a cursor rule published in the GitHub repository wyattowalsh/agents (5 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 387 tokens. 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.

Writing and docs
Related

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.

angular/angular · 0 tokens

dev-standard

Apache Superset development standards and guidelines for Cursor IDE.

apache/superset · 1,147 tokens

typescript

Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.

streamlit/streamlit · 4,669 tokens

coolify-ai-docs

Master reference to all Coolify AI documentation in .ai/ directory.

coollabsio/coolify · 1,426 tokens

python_lib

Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.

streamlit/streamlit · 0 tokens

specs

This directory contains product and tech specs for Streamlit features.

streamlit/streamlit · 0 tokens