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/copperdogma/cursor-project-bootstrapper/project-managementgit clone --depth 1 https://github.com/copperdogma/cursor-project-bootstrapperWhat 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.00852 | $0.00852 |
| Opus 5 | $0.00426 | $0.00426 |
| Sonnet 5 | $0.00170 | $0.00170 |
| Haiku 4.5 | $0.00085 | $0.00085 |
Grade A, and why
project-management 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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Programming Project Management
Overview
This file provides guidance for managing projects starting from the Building phase, after the project type is selected, and continuing into the Maintenance phase.
This document is used to guide project planning, management, and execution.
Phases
- Building: Implement features and functionality through stories.
- Maintenance: Manage updates, bug fixes, and improvements.
File Layout
/docs:- requirements.md: Defines project requirements. Formatting guidelines in
/docs/templates/requirements-template.md design.md: Outlines design details. Formatting guidelines in/docs/templates/design-template.mdarchitecture.md: Specifies architectural guidelines. Formatting guidelines in/docs/templates/design-architecture.mdstories.md: Lists all stories with IDs, titles, statuses, and links. Formatting guidelines in/docs/templates/design-stories.md/docs/stories/: Contains individual story files.
- requirements.md: Defines project requirements. Formatting guidelines in
/docs/templates/:story-template.md: Template for new story files.stories-template.md: Template for maintaining/docs/stories.md.
Workflow
Building Phase
- Story Management:
- Create new stories in
/docs/stories/using/docs/templates/story-template.md. - Add each story to
/docs/stories.mdwith a unique ID, title, status, and link. - Update statuses in
/docs/stories.mdas work progresses (e.g., "In Progress," "Done"). - Use the
build-story.mdcommand to work on stories - it maintains work logs within story files for complete implementation history.
- Create new stories in
- Implementation:
- Write code following
/docs/architecture.md,/docs/design.md, and@requirements.md.
- Write code following
- Progress Tracking:
- Log detailed implementation history in story work logs (see
build-story.mdcommand). - Check
docs/stories.mdto identify the current active story (status: "In Progress"). - Review the active story's work log for current task, progress, and blockers.
- Reflect status changes in
/docs/stories.md.
- Log detailed implementation history in story work logs (see
- Completion:
- Test the implementation (e.g., run code, verify functionality).
- Update the story file with final notes in the work log section.
- Mark the story as "Done" in
/docs/stories.md. - Confirm completion with the user and suggest the next story or phase transition.
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 · 88 lines · 852 tokens per session scan A f692c8b2e684
project-management is a cursor rule published in the GitHub repository copperdogma/cursor-project-bootstrapper (4 stars, last pushed 9mo ago), licensed MIT. It adds 852 tokens to every session, about $0.0043 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-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.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.