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.
git clone --depth 1 https://github.com/kubev2v/forklift-console-pluginWrote 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.
[](https://agentmods.dev/rules/kubev2v/forklift-console-plugin/new-component)<a href="https://agentmods.dev/rules/kubev2v/forklift-console-plugin/new-component"><img src="https://agentmods.dev/badge/rules/kubev2v/forklift-console-plugin/new-component/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.
<a href="https://agentmods.dev/rules/kubev2v/forklift-console-plugin/new-component"><img src="https://agentmods.dev/badge/rules/kubev2v/forklift-console-plugin/new-component.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00006 | $0.01036 |
| Opus 5.5 | $0.00002 | $0.00414 |
| Sonnet 5.5 | $0.00001 | $0.00207 |
| Haiku 4.5 | $0.00001 | $0.00104 |
Grade A, and why
new-component 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.
How it starts
The opening of the file, as written. The whole thing — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating a New Component
Invoke with: "create a component", "new component", "build a component for"
Follow this comprehensive workflow when creating new components. For coding conventions, see AGENTS.md.
1. Planning Phase
Understand Requirements
- What is the component's purpose?
- What data does it need?
- What actions can users perform?
- What states does it have (loading, error, empty)?
- How does it fit into the existing UI?
Identify Component Type
- Page Component: Top-level route component
- Container Component: Fetches data, manages state
- Presentational Component: Pure UI, receives props
- Modal Component: Overlay dialog
- Form Component: User input handling (react-hook-form)
- Error Boundary: Class component with componentDidCatch
Check Existing Patterns
- Look for similar components in codebase
- Identify reusable hooks from
@utils/or feature-specific hooks - Find existing utility functions
- Check PatternFly for appropriate components
- Use custom Select from
@components/common/Select(not PatternFly Select directly)
2. Folder Structure
src/{feature}/components/{component-name}/
ComponentName.tsx # Main component
component-name.scss # Styles
components/ # Sub-components
SubComponent.tsx
hooks/ # Component-specific hooks
useComponentLogic.ts
utils/ # Component-specific utilities
helpers.ts
constants.ts
Naming Conventions
- Folder: lowercase kebab-case (
provider-details-page) - Component file: PascalCase (
ProviderDetailsPage.tsx) - SCSS file: lowercase kebab-case (
provider-details-page.scss) - Hook files: camelCase with use prefix (
useProviderDetails.ts) - No barrel files -- import directly from the source file
3. Component Implementation
Component Structure Order
- Imports (external, then internal, then styles)
- Type definitions (using
type, notinterface) - Constants (if small, otherwise separate file)
- Component function (using
FCtype) - Default export
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.
- 1mo ago First seen · 153 lines · 6 tokens per session scan A e6aae8754ca9
new-component is a cursor rule published in the GitHub repository kubev2v/forklift-console-plugin (11 stars, last pushed today), licensed Apache-2.0. It adds 6 tokens to every session and 1,036 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.
Other cursor rules, from other repositories
windsurfrules
Create detailed components with these requirements.
state-management
Use the following stack. Do not introduce or recommend Redux or React Context for shared/global state.
backend
Backend development rules for TT Studio - AI model management backend.
tanstack-start-guide
TanStack Start best practices emphasizing client-first architecture, type safety, and modern React patterns.
tanstack-react-router_routing
TanStack Router: Routing.
project-structure
Folder layout for Next.js App Router and Vite + React variants.