What is new-features-planning?

A contribution workflow for planning and delivering new features or clients, including branches, focused commits, pull requests, and reviewers.

Use it when implementing a new feature or client, creating incremental commits, opening a pull request, adding reviewers, or managing a large task with a temporary checklist.

It sets a consistent process for recording changes and getting them reviewed, especially for larger feature work.

new-features-planning — Cursor rule for Cursor by 567-labs: A contribution workflow for planning and delivering new features…

Install

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.

agentmods

npx agentmods add rules/567-labs/instructor/new-features-planning

Clone the repo

git clone --depth 1 https://github.com/567-labs/instructor

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/rules/567-labs/instructor/new-features-planning.svg)](https://agentmods.dev/rules/567-labs/instructor/new-features-planning)

Your own site

<a href="https://agentmods.dev/rules/567-labs/instructor/new-features-planning"><img src="https://agentmods.dev/badge/rules/567-labs/instructor/new-features-planning.svg" alt="Measured on agentmods" height="20"></a>

Per session 488 This file is loaded in full into every session.

When invoked 488 The same file — it is already loaded in full.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What 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.00488	$0.00488
Opus 5	$0.00244	$0.00244
Sonnet 5	$0.00098	$0.00098
Haiku 4.5	$0.00049	$0.00049

Measured 4d ago against content hash a71203e7cc37, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

new-features-planning 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 4d 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.

.cursor/rules/new-features-planning.mdc · 46 lines

What it actually says

When being asked to make new features, make sure that you check out from main a new branch and make incremental commits
- Use conventional commit format: <type>(<scope>): <description>
  - Types: feat, fix, docs, style, refactor, perf, test, chore
  - Example: feat(validation): add email validation function
  - Keep commits focused on a single change
  - Write descriptive commit messages in imperative mood
- Use git commit -m "type(scope): subject" -m "body" -m "footer" for multiline commits
If the feature is very large, create a temporary todo.md

And start a pull request using gh

Create PRs with multiline bodies using:

gh pr create --title "feat(component): add new feature" --body "$(cat <<EOF
## Description
Detailed explanation of the changes

## Changes
- List important changes
- Another change

## Testing
How this was tested

This PR was written by [Cursor](cursor.com)
EOF
)" -r jxnl,ivanleomk

Or use the -F flag with a file: gh pr create -F pr_body.md

Make sure to include This PR was written by [Cursor](mdc:cursor.com)
Add default reviewers:
- Use gh pr edit <id> --add-reviewer jxnl,ivanleomk
- Or include -r jxnl,ivanleomk when creating the PR
use gh pr view <id> --comments | cat to view all the comments
For PR updates:
- Do not directly commit to an existing PR branch
- Instead, create a new PR that builds on top of the original PR's branch
- This creates a "stacked PR" pattern where:
  1. The original PR (base) contains the initial changes
  2. The new PR (stack) contains only the review-related updates
  3. Once the base PR is merged, the stack can be rebased onto main

Changes

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.

4d ago First seen · 46 lines · 488 tokens per session scan A a71203e7cc37

Subscribe to this mod's changes

new-features-planning is a cursor rule published in the GitHub repository 567-labs/instructor (13,825 stars, last pushed yesterday), licensed MIT. It adds 488 tokens to every session, about $0.0024 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.

Planning Python openai openai-function-calli openai-functions pydantic-v2 validation

new-features-planning

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other cursor rules, from other repositories

backend-rules

python_tests

sqlmodel

backend-python

python

python