Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/hiromaily/docs-ssotnpx agentmods add rules/hiromaily/docs-ssot/generalWrote 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/hiromaily/docs-ssot/general)<a href="https://agentmods.dev/rules/hiromaily/docs-ssot/general"><img src="https://agentmods.dev/badge/rules/hiromaily/docs-ssot/general/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.
<a href="https://agentmods.dev/rules/hiromaily/docs-ssot/general"><img src="https://agentmods.dev/badge/rules/hiromaily/docs-ssot/general.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.01820 | $0.01820 |
| Opus 5.5 | $0.00728 | $0.00728 |
| Sonnet 5.5 | $0.00364 | $0.00364 |
| Haiku 4.5 | $0.00182 | $0.00182 |
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 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.
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.mdCLAUDE.mdAGENTS.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) |
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.
- 1mo ago First seen · 190 lines · 1,820 tokens per session scan A 09352af98351
general is a cursor rule published in the GitHub repository hiromaily/docs-ssot (2 stars, last pushed 6mo ago), licensed MIT. It adds 1,820 tokens to every session, about $0.0073 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-31.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
shared-plane-packages
Pattern for creating shared plane packages that serve both migration and runtime planes.