agentmods.dev

feature-request

feature-request is a cursor rule for Cursor from rm2thaddeus/Pixel_Detective. It costs 3 tokens per session (1,200 once invoked), scanned A, original, MIT.

A rulebook for implementing features with repository discovery, requirements planning, testing criteria, and integrations with external development tools.

In plain words
What is it for?
Use it when adding a feature that may involve existing modules, APIs, databases, documentation, frontend behavior, or backend logic.
Why use it?
It gives feature work a repeatable process for understanding existing code and checking technical, UI, backend, and performance needs.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

not rated 21repo 8mo ago A scan 3 tokens original MIT

Good fit Use it when adding a feature that may involve existing modules, APIs, databases, documentation, frontend behavior, or backend logic.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/rm2thaddeus/pixel_detective/feature-request
View source ↗ rm2thaddeus/Pixel_Detective rm2thaddeus.github.io
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.

Clone the repo
git clone --depth 1 https://github.com/rm2thaddeus/Pixel_Detective

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 feature-request

README.md
[![agentmods](https://agentmods.dev/badge/rules/rm2thaddeus/pixel_detective/feature-request/github.svg)](https://agentmods.dev/rules/rm2thaddeus/pixel_detective/feature-request)
Your own site
<a href="https://agentmods.dev/rules/rm2thaddeus/pixel_detective/feature-request"><img src="https://agentmods.dev/badge/rules/rm2thaddeus/pixel_detective/feature-request/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for feature-request

Your own site · 80×15
<a href="https://agentmods.dev/rules/rm2thaddeus/pixel_detective/feature-request"><img src="https://agentmods.dev/badge/rules/rm2thaddeus/pixel_detective/feature-request.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 3 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,200 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00003 $0.01200
Opus 5.5 $0.00001 $0.00480
Sonnet 5.5 $0.00001 $0.00240
Haiku 4.5 $0.00000 $0.00120

Measured 1mo ago against content hash f09bb9205dbf, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

feature-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 1mo 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/feature-request.mdc · 97 lines

How it starts

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

Feature Implementation with MCP Integration

Reference: Follow @use-mcp-servers for detailed MCP workflows and best practices

MCP-Enhanced Feature Development Workflow

1. Map Context & Discovery

  • Project Structure: tree -L 4 --gitignore | cat - identify modules/APIs
  • Existing Patterns: Use codebase_search to find similar features and reusable components
  • Dependencies Analysis: Use grep_search for exact symbol/import matches
  • Documentation Research: Use Context7 MCP to gather API docs for new libraries/frameworks needed
  • Database Schema Review: Use Supabase MCP to understand existing data structures if feature involves data

2. Specify Requirements & Architecture

  • Break feature into testable criteria, use cases, and constraints
  • Frontend Requirements: Consider UI/UX implications, accessibility standards
  • Backend Requirements: Define data models, API endpoints, business logic
  • Integration Points: Identify touchpoints with existing systems
  • Performance Criteria: Set measurable performance benchmarks
  • Documentation Standards: Plan documentation updates per @use-mcp-servers guidelines

3. Leverage Reusability & Research

  • Component Discovery: Use codebase_search and grep_search to find reusable patterns
  • Library Integration: Use Context7 MCP to:
    • Research best practices for new dependencies
    • Find code examples and implementation patterns
    • Understand API compatibility and version requirements
  • Database Patterns: Use Supabase MCP to identify reusable query patterns and schema structures
  • Similar Features: Use GitHub MCP to search project history for related implementations

4. Plan Changes & MCP Strategy

  • File Inventory: List all files to edit/create with specific paths
  • Cross-Cutting Concerns: Identify impacts on authentication, logging, error handling, testing
  • MCP Server Selection: Choose appropriate MCP servers per @use-mcp-servers task-based guide:
    • Frontend Features: Browser Tools + Browser Control MCP for testing/validation
    • Backend Features: Supabase MCP for database operations
    • API Integration: Context7 MCP for documentation + GitHub MCP for implementation
    • Full-Stack Features: Coordinate multiple MCP servers
  • Branch Strategy: Plan feature branch creation via GitHub MCP

Read the full file on GitHub · 97 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. 1mo ago First seen · 97 lines · 3 tokens per session scan A f09bb9205dbf

Subscribe to this mod's changes

feature-request is a cursor rule published in the GitHub repository rm2thaddeus/Pixel_Detective (21 stars, last pushed 8mo ago), licensed MIT. It adds 3 tokens to every session and 1,200 once invoked, about $0.0000 per session on Opus 5.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
Related

Other cursor rules, from other repositories

ponytail

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

DietrichGebert/ponytail · 604 tokens

angular-20

This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.

angular/angular · 0 tokens

dev-standard

Apache Superset development standards and guidelines for Cursor IDE.

apache/superset · 1,147 tokens

prefer-assertions-over-defensive-checks

Prefer assertions over defensive checks when data is guaranteed to be valid.

prisma/orm · 0 tokens

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.

prisma/orm · 0 tokens

shared-plane-packages

Pattern for creating shared plane packages that serve both migration and runtime planes.

prisma/orm · 0 tokens