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/kubev2v/forklift-console-plugin/feature-developmentgit clone --depth 1 https://github.com/kubev2v/forklift-console-pluginWhat 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.00010 | $0.01344 |
| Opus 5 | $0.00005 | $0.00672 |
| Sonnet 5 | $0.00002 | $0.00269 |
| Haiku 4.5 | $0.00001 | $0.00134 |
Grade A, and why
feature-development 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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Development Workflow
Invoke with: "start a new feature", "work on MTV-XXX end to end", "full development workflow"
This is the complete workflow from picking up a Jira ticket to submitting a PR.
1. Workflow Overview
1. PICK UP TICKET
"Start working on MTV-1885"
Fetch ticket, understand requirements, plan approach
2. PLAN IMPLEMENTATION
"Help me plan the implementation"
Identify files to modify, components to create
3. IMPLEMENT
"Create the component", "Add the feature"
Write code following project standards (AGENTS.md)
4. TEST
"Test my changes", "Add unit tests"
Unit tests, interactive testing with Playwright
5. REVIEW
"Review my code"
Multi-perspective review (dev, UX, QE, security, Forklift expert)
6. PREPARE PR
"Prepare this for PR"
Quality checks, PR description, update Jira
2. Phase 1: Pick Up Ticket
Get the Ticket
"Start working on MTV-1885"
I will:
- Fetch ticket details from Jira
- Summarize requirements - what needs to be built
- Identify acceptance criteria - definition of done
- Check dependencies - blockers, related tickets
Understand the Context
- Epic/parent story
- Related tickets and comments
- Attached mockups or designs
3. Phase 2: Plan Implementation
Identify Code Changes
"Help me plan how to implement this"
I will:
- Find relevant existing code - similar components, utilities
- Identify files to modify - which components are affected
- Suggest new files needed - new components, hooks, utils
- Recommend approach - how to structure the solution
Consider Architecture
- Does this fit existing patterns?
- Should this be a reusable component?
- What's the impact on other features?
- Which provider types are affected?
4. Phase 3: Implement
Create Components
Following new-component.mdc workflow:
- Proper folder structure
- TypeScript types (using
type, notinterface) - SCSS styles with BEM
- Translation support (
useForkliftTranslation) - Accessibility requirements
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 · 237 lines · 10 tokens per session scan A aadadad0957f
feature-development is a cursor rule published in the GitHub repository kubev2v/forklift-console-plugin (11 stars, last pushed 2d ago), licensed Apache-2.0. It adds 10 tokens to every session and 1,344 once invoked, about $0.0001 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.
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.
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.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
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.