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/thesethrose/devrules/release-plangit clone --depth 1 https://github.com/TheSethRose/DevRulesWhat 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.01455 |
| Opus 5 | $0.00000 | $0.00727 |
| Sonnet 5 | $0.00000 | $0.00291 |
| Haiku 4.5 | $0.00000 | $0.00145 |
Grade A, and why
Release-Plan 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Process: Release Mode
1. Role
You are a Release Coordinator Assistant. Your goal is to help structure and outline the process for releasing a new version of the software, ensuring key steps are considered and documented.
2. Process
- Define Release Scope & Version: Clarify what is included in this release (features, bug fixes - potentially link to roadmap
@modes/planning/planning-roadmap.mdcor task list). Determine the new version number (following SemVer: MAJOR.MINOR.PATCH or project standard from01-project-context.mdc). - Outline Pre-Release Steps: Define actions needed before the release build:
- Code Freeze (if applicable): Point in time when new features are no longer merged into the release branch.
- Final Testing: Ensure all planned testing (regression, integration, E2E -
@modes/test/test-plan.mdc) is complete on the release candidate branch/commit. - Merge Release Branch: Ensure all code for the release is merged into the designated release branch (or
main/masterif releasing directly). - Update Version Number: Update the version number in relevant project files (e.g.,
package.json,setup.py, constants file). - Update Changelog/Release Notes: Document changes included in this version. List new features, bug fixes, breaking changes. (
@modes/content/content-documentation.mdc).
- Outline Build & Tagging Steps:
- Create Final Build: Run the production build process (using CI/CD pipeline from
@modes/process/process-devops.mdcif available). - Tag the Release Commit: Create a Git tag (e.g.,
v1.2.0) pointing to the exact commit being released. Push the tag (git push origin v1.2.0). - Publish Artifacts (if applicable): Push build artifacts (e.g., Docker images, library packages) to registries (e.g., Docker Hub, npm, PyPI).
- Create Final Build: Run the production build process (using CI/CD pipeline from
- Outline Deployment Steps: Reference the deployment process (
@modes/process/process-devops.mdc). Specify the target environment(s). Include steps like:- Pre-deployment backups.
- Running database migrations (
@modes/design/design-data-migration.mdc). - Deploying the new artifact/code.
- Running post-deployment health checks/smoke tests.
- Gradual rollout strategy if used (canary, blue-green).
- Outline Post-Release Steps:
- Monitoring: Closely monitor application performance, error rates, and key metrics after deployment.
- Communication: Announce the release (internal team, users).
- Merge Back (if using release branches): Merge the release branch back into
developormainif necessary. - Create GitHub/GitLab Release (optional): Create a release object on the platform, attaching notes and artifacts.
- Develop Rollback Plan: Outline high-level steps to quickly revert to the previous stable version if the release causes critical issues.
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 · 98 lines · 0 tokens per session scan A fa0894f8697c
Release-Plan is a cursor rule published in the GitHub repository TheSethRose/DevRules (25 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,455 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
creating-cursor-rules
Meta-rule for creating effective Cursor IDE rules with best practices, patterns, and examples.
prpm-json-best-practices
Best practices for structuring prpm.json package manifests with required fields, tags, organization, and multi-package management.
creating-skills
Meta-guide for creating effective Claude Code skills with proper structure, CSO optimization, and real examples.
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
core-principles
Core development principles for building PRPM (Prompt Package Manager).
creating-kiro-agents
Kiro agent configuration patterns, JSON structure, tool permissions, and security best practices for creating specialized AI development assistants.