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/docxology/template/cursorrulesgit clone --depth 1 https://github.com/docxology/templateWhat 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 | $0.01159 | $0.01159 |
| Opus 5 | $0.00580 | $0.00580 |
| Sonnet 5 | $0.00232 | $0.00232 |
| Haiku 4.5 | $0.00116 | $0.00116 |
Grade A, and why
cursorrules 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 yesterday.
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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor and IDE agents — repository guidance
Use this file together with README.md (onboarding), CLAUDE.md (commands and patterns for Claude Code), and AGENTS.md (full system reference, troubleshooting, configuration).
What to read first
| Goal | Primary doc |
|---|---|
| Clone → run pipeline | README.md Quickstart, docs/RUN_GUIDE.md |
| Exact shell commands, CI mirror, examples | CLAUDE.md |
| Pipeline stages, validation, multi-project rules, deep TOC | AGENTS.md |
| Directory-specific APIs and conventions | AGENTS.md / README.md within that subdirectory (each projects/<name>/manuscript/ has its own AGENTS.md) |
Public project names (infrastructure.project.public_scope) |
docs/_generated/active_projects.md |
| Live counts and coverage claims | docs/_generated/COUNTS.md (refresh via measured pytest + scripts/docgen/active_projects.py; see docs/_generated/README.md) |
Architecture (non-negotiable)
- Thin orchestrators: Business logic belongs only in
infrastructure/(generic) orprojects/{name}/src/(domain). Rootscripts/andprojects/{name}/scripts/coordinate I/O, subprocesses, and plotting — they call tested functions; they do not own algorithms. - Layer 1:
infrastructure/, reposcripts/,tests/infra_tests/. - Layer 2: Each active project under
projects/<name>/withsrc/,tests/,manuscript/,scripts/,output/. Final deliverables are copied tooutput/<name>/. - Canonical exemplars (always tracked, per
infrastructure.project.public_scope.PUBLIC_PROJECT_NAMES):template_active_inference,template_advanced_literature_review,template_autopoiesis,template_autoresearch_project,template_autoscientists,template_code_project,template_data_descriptor,template_eda_notebook,template_formal,template_gold_refinement,template_literature_meta_analysis,template_madlib,template_methods_paper,template_newspaper,template_pitch_deck,template_pools_rules_tools,template_prose_project,template_redacted_report,template_registered_report,template_search_project,template_sia,template_storybook,template_template,template_textbook. Authoritative roster:docs/_generated/active_projects.md. Do not assume other folder names underprojects/exist in every checkout; use discovery output above. output/is disposable: Bothprojects/<name>/output/and rootoutput/<name>/are regenerated by the pipeline — do not commit their contents.
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.
- yesterday First seen · 65 lines · 1,159 tokens per session scan A cd1160810b3e
cursorrules is a cursor rule published in the GitHub repository docxology/template (19 stars, last pushed yesterday), licensed Apache-2.0. It adds 1,159 tokens to every session, about $0.0058 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-30.
Other cursor rules, from other repositories
project
Core project context for ai-context-kit.
project
Project conventions - canonical source is AGENTS.md.
breakthrough-loop
Research discipline - breakthrough loop with a hard-to-fool harness.
core
The engineering contract for this repo lives in AGENTS.md (auto-loaded). Follow it. This rule only adds Cursor-specific behavior so the contract is not duplicated token-for-token on every request.
debugging
Debugging discipline. Apply when investigating a bug, test failure, or unexpected behavior.
frontend
UI/component conventions. Apply when building or changing user-facing frontend code.