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/ryanrawlingswang/llm-rules/project-mangementgit clone --depth 1 https://github.com/ryanrawlingswang/llm-rulesWhat 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.00327 | $0.00327 |
| Opus 5 | $0.00163 | $0.00163 |
| Sonnet 5 | $0.00065 | $0.00065 |
| Haiku 4.5 | $0.00033 | $0.00033 |
Grade A, and why
project-mangement 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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- project-management — 100% identical, 1 lines differ
What it actually says
Rules File: Progress Tracking System
Core Rules
-
Always read feature.md first
- Read and understand the complete feature requirements
- Identify all tasks and deliverables outlined in feature.md
- Use this as the source of truth for what needs to be accomplished
-
Always read progress.md before starting work
- Check current status of all tasks
- Identify what has been completed
- Identify what remains to be done
- Avoid duplicating completed work
-
Update progress.md after completing any task
- Mark completed tasks with status and timestamp
- Add detailed notes about what was accomplished
- Update percentage completion if applicable
- Note any blockers or issues encountered
-
Progress.md Structure Requirements
- Maintain clear task breakdown from feature.md
- Use consistent status indicators (TODO, IN_PROGRESS, COMPLETED)
- Include timestamps for all status changes
- Provide brief descriptions of work completed
- Track overall feature completion percentage
-
Task Completion Workflow
- Read feature.md → Read progress.md → Complete task → Update progress.md
- Never skip the progress update step
- Be specific about what was accomplished in each update
- Reference specific files, functions, or components modified
-
Quality Standards
- Ensure progress updates are accurate and detailed
- Maintain chronological order of updates
- Keep progress.md synchronized with actual work completed
- Use clear, professional language in all updates
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.
- 3d ago First seen · 45 lines · 327 tokens per session scan A 7ccd82546238
project-mangement is a cursor rule published in the GitHub repository ryanrawlingswang/llm-rules (17 stars, last pushed 2mo ago), licensed MIT. It adds 327 tokens to every session, about $0.0016 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
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.