agentmods.dev

change-request

change-request is a cursor rule for Cursor from danielvm-git/bigpowers. It costs 43 tokens per session (1,188 once invoked), scanned A, original, MIT.

Add a new requirement or reorder epics by WSJF against specs/release-plan.yaml and epic capsule directories. Modes Add and Reorder. Use when a new requirement arrives mid-release or the plan needs prioritization.

Cursor rule for Cursor

not rated 163 2d ago A scan 43 tokens MIT
View the source file danielvm-git/bigpowers
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/danielvm-git/bigpowers/change-request
Clone the repo
git clone --depth 1 https://github.com/danielvm-git/bigpowers

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.

agentmods badge for change-request

README.md
[![agentmods](https://agentmods.dev/badge/rules/danielvm-git/bigpowers/change-request.svg)](https://agentmods.dev/rules/danielvm-git/bigpowers/change-request)
Your own site
<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/change-request"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/change-request.svg" alt="Measured on agentmods" height="20"></a>
Per session 43 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,188 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.

ModelPer sessionOnce invoked
Fable 5 $0.00043 $0.01188
Opus 5 $0.00022 $0.00594
Sonnet 5 $0.00009 $0.00238
Haiku 4.5 $0.00004 $0.00119

Measured today against content hash 9ec003c1ebd3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

change-request 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 today.

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/change-request.mdc · 121 lines

How it starts

The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.

story: e45s29

story: e20s01

Change Request

HARD GATE — specs/release-plan.yaml must exist before running either mode. If it doesn't, run plan-release first.

→ verify: test -f specs/release-plan.yaml

Two modes. State which one you want or the skill will ask.

Mode A — Add

Intake a new requirement mid-flight without disrupting work in progress.

  1. Capture: What is the change? What problem does it solve?
  2. Locate: Which existing stories in specs/epics/ does it affect or replace?
  3. Draft: Add story + tasks[] with Gherkin-style AC in epic YAML (each task has verify). Tag requirement deltas: ADDED / MODIFIED / REMOVED / RENAMED with before/after for non-ADDED changes (e45s29).
  4. Place: Append story under existing epic capsule, or create specs/epics/eNN-slug.yaml and register in release-plan.yaml epics[].
  5. Score: Compute WSJF; note if it outranks in-progress work.

→ verify: grep -c 'stories:' specs/epics/*/epic.yaml

Mode B — Reorder

Value-engineering pass over the full release using WSJF.

See REFERENCE.md for the full WSJF scoring rubric.

  1. Score each epic/story: BV + TC + RR / Job Size.
  2. Re-sort release-plan.yaml epics[] and per-epic wsjf fields.
  3. Flag cut candidates: WSJF < 1.5.
  4. Update specs/release-plan.yaml and epic wsjf keys with rationale.
  5. Report the delta.

→ verify: grep -c 'wsjf' specs/release-plan.yaml specs/epics/*/epic.yaml

Conversational Mode

If the user's request is in natural language and does not match the structured format of Mode A or Mode B, enter Conversational Mode to extract the change parameters through interactive dialogue.

5-Step Flow

  1. Capture: Parse the natural-language request for what, why, and where. Ask at most 3 clarifying questions before drafting.
  2. Locate: Identify which epic or capability in specs/epics/ the request affects or replaces.
  3. Draft: Present a structured draft of the proposed story and tasks for user confirmation.
  4. Score: Estimate the WSJF score and explain the calculation so the user understands the priority.
  5. Place: Confirm the final epic placement with the user before writing files.

Read the full file on GitHub · 121 lines

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.

  1. today First seen · 121 lines · 43 tokens per session scan A 9ec003c1ebd3

Subscribe to this mod's changes

change-request is a cursor rule published in the GitHub repository danielvm-git/bigpowers (163 stars, last pushed 2d ago), licensed MIT. It adds 43 tokens to every session and 1,188 once invoked, about $0.0002 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-09-03.

Git and workflowPlanningai-agentsautomationbmadclaude-codeclean-codecursor-rules
Related

Other cursor rules, from other repositories

ponytail

Ponytail, lazy senior dev mode. Always pick the simplest solution that works.

DietrichGebert/ponytail · 576 tokens

app-router-patterns

Next.js 14+ App Router patterns — Server Components, Client Components, Route Handlers, Server Actions, and metadata API.

tugkanboz/awesome-cursorrules · 2,554 tokens

00-project-rules

ContextOS core project rules and role orchestration.

kok-o/koko-contextos-agents · 3,607 tokens

context-os

ContextOS rules for context-os.

kok-o/koko-contextos-agents · 6 tokens

database

Database architecture, schema design, Prisma, Drizzle ORM, indexing strategies, migrations, and N+1 query resolution.

kok-o/koko-contextos-agents · 24 tokens

vue

Rules for Vue (2 and 3) single-file components.

inboxpraveen/Minimize-Cursor-Cost · 0 tokens