general

Project rules for docs-ssot, a command-line tool that generates several documentation files from shared Markdown source files.

In plain words
What is it for?
Use them when changing documentation sources, understanding the repository layout, and regenerating README.md, CLAUDE.md, or AGENTS.md.
Why use it?
They prevent edits from being lost when generated files are rebuilt and preserve one authoritative place for documentation content.

Cursor rule for Cursor

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/hiromaily/docs-ssot/general
Clone the repo
git clone --depth 1 https://github.com/hiromaily/docs-ssot

Made for: Cursor.

Per session 1,820 This file is loaded in full into every session.
When invoked 1,820 The same file — it is already loaded in full.
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.01820 $0.01820
Opus 5 $0.00910 $0.00910
Sonnet 5 $0.00364 $0.00364
Haiku 4.5 $0.00182 $0.00182

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

Security

Grade A, and why

general 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/general.mdc · 190 lines

How it starts

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

General Development Rules for docs-ssot

Project Purpose

docs-ssot is a CLI tool that generates documentation files (README.md, CLAUDE.md, AGENTS.md) from modular Markdown source files using a template-based composition system. It implements the Single Source of Truth (SSOT) principle for documentation.


Critical Rule: Never Edit Generated Files

The following files are build artifacts — do NOT edit them directly:

  • README.md
  • CLAUDE.md
  • AGENTS.md

Always edit the source files in docs/ and regenerate with make docs.


Repository Structure

docs-ssot/
├── cmd/docs-ssot/main.go       # CLI entry point (build command)
├── internal/
│   ├── config/config.go        # YAML config loader (Config, Target types)
│   ├── generator/generator.go  # Build orchestrator (Build func)
│   └── processor/              # Include resolver + transformer pipeline (ProcessFile func)
├── docs/                       # Source Markdown files (SSOT — edit here)
│   ├── 01_project/             # Project context and vision
│   ├── 02_product/             # Product concept and features
│   ├── 03_architecture/        # System architecture and pipeline
│   ├── 04_development/         # Setup, testing, linting guides
│   ├── 05_ai/                  # AI tool-specific docs (Claude, Cursor, Codex, etc.)
│   └── 06_reference/           # Commands and directory reference
├── template/                   # Document templates (define output structure)
│   ├── README.tpl.md
│   ├── CLAUDE.tpl.md
│   └── AGENTS.tpl.md
├── docsgen.yaml                # Build targets: template → output mapping
├── Makefile                    # Build, lint, test, docs commands
└── .golangci.yml               # Linting configuration (46+ linters)

Go Package Responsibilities

Package File Responsibility
main cmd/docs-ssot/main.go CLI arg parsing, dispatch to generator.Build()
config internal/config/config.go Load/save docsgen.yaml into Config{Targets []Target}
generator internal/generator/generator.go Iterate targets, call include resolver, write output
processor internal/processor/processor.go Include resolution, transformer pipeline (ProcessFile, Transformer, Apply)
agentscan internal/agentscan/agentscan.go Detect AI tools (.claude/, .cursor/, .github/, .codex/) and collect agent files
frontmatter internal/frontmatter/frontmatter.go Parse/strip/generate YAML frontmatter for different tool formats
migrate internal/migrate/agents.go Agent-aware migration pipeline (scan → section → template → config → verify)

Read the full file on GitHub · 190 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. 2d ago First seen · 190 lines · 1,820 tokens per session scan A 09352af98351

Subscribe to this mod's changes

general is a cursor rule published in the GitHub repository hiromaily/docs-ssot (2 stars, last pushed 4mo ago), licensed MIT. It adds 1,820 tokens to every session, about $0.0091 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.