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.
npx agentmods add rules/hiromaily/docs-ssot/vitepressgit clone --depth 1 https://github.com/hiromaily/docs-ssotWrote 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/vitepress)<a href="https://agentmods.dev/rules/hiromaily/docs-ssot/vitepress"><img src="https://agentmods.dev/badge/rules/hiromaily/docs-ssot/vitepress.svg" alt="Measured on agentmods" 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.00000 | $0.00412 |
| Opus 5 | $0.00000 | $0.00206 |
| Sonnet 5 | $0.00000 | $0.00082 |
| Haiku 4.5 | $0.00000 | $0.00041 |
Grade A, and why
vitepress 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 5d 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.
What it actually says
VitePress Documentation Site Rules
Package Manager: Bun Only
This project uses Bun as the JavaScript package manager and runtime for the VitePress documentation site. Do not use npm, pnpm, or yarn.
# ✅ Correct
cd docs && bun install
cd docs && bun run dev
cd docs && bun run build
# ❌ Wrong
cd docs && npm install
cd docs && pnpm install
cd docs && yarn install
The lockfile is docs/bun.lock. Do not create package-lock.json, pnpm-lock.yaml, or yarn.lock.
VitePress Commands
Use the Makefile targets for VitePress operations:
| Command | Purpose |
|---|---|
make install-docs |
Install VitePress dependencies |
make vitepress-dev |
Start development server |
make vitepress-build |
Build static site |
make vitepress-preview |
Preview production build |
Content Source: template/sections/
VitePress pages use @include directives to pull content from template/sections/. Do not duplicate content into docs/ pages — each page should be a thin wrapper:
# Page Title
<!--@include: ../../template/sections/category/file.md-->
This ensures the VitePress site, README.md, CLAUDE.md, and all other generated files share the same source content.
Adding a New VitePress Page
- Create a
.mdfile in the appropriatedocs/subdirectory - Add an
@includedirective pointing to the source intemplate/sections/ - Register the page in
docs/.vitepress/config.ts(sidebar and/or nav) - Run
make vitepress-buildto 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.
- 5d ago First seen · 56 lines · 0 tokens per session scan A cf0764349761
vitepress is a cursor rule published in the GitHub repository hiromaily/docs-ssot (2 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 412 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.
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.
cli-error-handling
CLI command error handling patterns.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.