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/bluewings1211/codebase-rag/generate-tasksgit clone --depth 1 https://github.com/bluewings1211/codebase-RAGWhat 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.00935 |
| Opus 5 | $0.00000 | $0.00467 |
| Sonnet 5 | $0.00000 | $0.00187 |
| Haiku 4.5 | $0.00000 | $0.00093 |
Grade A, and why
generate-tasks 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.
Copies of this mod
5 near-identical copies found in the catalogue:
- process_task_list — 97% identical, 16 lines differ
- generate-tasks — 95% identical, 12 lines differ
- generate-tasks — 94% identical, 16 lines differ
- generate_tasks — 88% identical, 19 lines differ
- 1001-generate-tasks-from-prd — 86% identical, 56 lines differ
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rule: Generating a Task List from a PRD
Goal
To guide an AI assistant in creating a detailed, step-by-step task list in Markdown format based on an existing Product Requirements Document (PRD). The task list should guide a developer through implementation.
Output
- Format: Markdown (
.md) - Location:
/tasks/ - Filename:
tasks-[prd-file-name].md(e.g.,tasks-prd-user-profile-editing.md)
Process
- Receive PRD Reference: The user points the AI to a specific PRD file
- Analyze PRD: The AI reads and analyzes the functional requirements, user stories, and other sections of the specified PRD.
- Phase 1: Generate Parent Tasks: Based on the PRD analysis, create the file and generate the main, high-level tasks required to implement the feature. Use your judgement on how many high-level tasks to use. It's likely to be about 5. Present these tasks to the user in the specified format (without sub-tasks yet). Inform the user: "I have generated the high-level tasks based on the PRD. Ready to generate the sub-tasks? Respond with 'Go' to proceed."
- Wait for Confirmation: Pause and wait for the user to respond with "Go".
- Phase 2: Generate Sub-Tasks: Once the user confirms, break down each parent task into smaller, actionable sub-tasks necessary to complete the parent task. Ensure sub-tasks logically follow from the parent task and cover the implementation details implied by the PRD.
- Identify Relevant Files: Based on the tasks and PRD, identify potential files that will need to be created or modified. List these under the
Relevant Filessection, including corresponding test files if applicable. - Generate Final Output: Combine the parent tasks, sub-tasks, relevant files, and notes into the final Markdown structure.
- Save Task List: Save the generated document in the
/tasks/directory with the filenametasks-[prd-file-name].md, where[prd-file-name]matches the base name of the input PRD file (e.g., if the input wasprd-user-profile-editing.md, the output istasks-prd-user-profile-editing.md).
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 · 71 lines · 0 tokens per session scan A bb6194668b9e
generate-tasks is a cursor rule published in the GitHub repository bluewings1211/codebase-RAG (15 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 935 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-30.
Other cursor rules, from other repositories
cursorrules
You are an expert in developing information retrieval, re-ranking, and retrieval-augmented generation (RAG) systems using Python, with a focus on PyTorch and state-of-the-art NLP models.
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.