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/systemowiec/ai-agents-workspace-starter/docsgit clone --depth 1 https://github.com/systemowiec/ai-agents-workspace-starterWhat 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.00000 | $0.00332 |
| Opus 5 | $0.00000 | $0.00166 |
| Sonnet 5 | $0.00000 | $0.00066 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
docs 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.
What it actually says
Docs Rules
Specifications
Spec required for: major features, global fixes, architectural changes. Specs are not required for small fixes - they can be prepared retroactively if needed.
Rules
- Specs numbered sequentially per layer:
ARCH-001,BE-001,FE-001 - Spec in
docs/specs/{layer}/{PREFIX}-NNN/{PREFIX}-NNN_title.md - Report in
docs/specs/{layer}/{PREFIX}-NNN/impl-{role}.md - DONE status - only after review approval (quality-gate)
- NEVER add hourly estimates
Templates
docs/templates/_spec.md- Specificationdocs/templates/_spec-report.md- Implementation report
Workflow
- Creating spec:
.agents/workflows/create-spec.md - Closing spec:
.agents/workflows/complete-spec.md
Agent Reports
- Scope:
docs/specs/{layer}/{PREFIX}-NNN/scope-{role}.md - Implementation:
docs/specs/{layer}/{PREFIX}-NNN/impl-{role}.md - Review:
docs/specs/{layer}/{PREFIX}-NNN/review-{role}.md
Conventions
- Documentation language: English
- Code language: English
- Mermaid for diagrams
- Markdown tables instead of ASCII art
- No hourly estimates in any document
- No typographic dashes - only
-(ASCII 45) - File links: relative paths
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.
- 2d ago First seen · 46 lines · 0 tokens per session scan A 7ab721d5e0b2
docs is a cursor rule published in the GitHub repository systemowiec/ai-agents-workspace-starter (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 332 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
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.
family-instance-domain-actions
Family instance domain action implementation patterns.